Granted Patent B2

US 12,401,711 · App. 18/732,409 · Granted Aug 26, 2025

Inventors: Erik Palvadeau (Nanterre, FR); Nicolas Vigot (Blagnac, FR); Marc Tang (Nanterre, FR); Emeric Leblin (Nanterre, FR); Pierre Ibos (Blagnac, FR); Thierry Catalan (Nanterre, FR)

Assignee: ADP, Inc.

H04L67/02H04L63/029H04L41/22

Abstract

Claims (104)

1. A system, comprising:

one or more processors, coupled with memory, to:

receive a request to publish a resource on a digital repository;

present, via a user interface, an aspect of the request;

receive, via the user interface, an input subsequent to presenting the aspect of the request;

determine, based on the input, that a format of the request is valid;

cause, responsive to determination that the format of the request is valid, an execution of a test on the request, wherein the test comprises to:

convert the request to at least one application programming interface (API) call;

receive, responsive to transmission of the at least one API call, at least one API response that corresponds to a result of execution of the at least one API call; and

determine, using the at least one API response, a status of the resource; and

send the status of the resource to a computing device.

2. The system of claim 1 , wherein the at least one API response includes a first format selected based on a backend server successfully implementing a configuration change of the request, and wherein the at least one API response includes a second format selected based on the backend server unsuccessfully implementing the configuration change.

3. The system of claim 1 , wherein the one or more processors further:

generate information associated with a first configuration change of the request;

store, in a database, the information associated with the first configuration change; and

update, responsive to receipt of at least one second API response, the information associated with the first configuration change to reflect a second configuration change.

4. The system of claim 1 , wherein the resource includes at least one of:

a uniform resource locator (URL);

a uniform resource identifier (URI);

a service; or

a subscription.

5. The system of claim 1 , wherein the request includes at least one of:

a request to create the resource;

a request to modify the resource;

a request to view the resource;

a request for workflow approval of the resource; or

a request to delete the resource.

6. The system of claim 1 , wherein the at least one API call includes at least one of:

a web service API;

a Firewall API;

a certificate API;

a VIP API; and

a DNS API.

7. The system of claim 1 , wherein the request is received from the computing device, and wherein the request is instantiated by at least one of:

one or more interactions with a web browser presented by the computing device; or

a programmatic API call transmitted by the computing device.

8. The system of claim 1 , wherein the format of the request includes at least one of:

a URL name;

a service name;

a LDAP name;

a server identifier;

a VIP identifier; or

a port number.

9. The system of claim 1 , wherein the one or more processors further:

cause, via an API call to a server, execution of a configuration change of the request; or

cause, via an API call to a platform, execution of the configuration change of the request.

10. The system of claim 1 , wherein the one or more processors further:

execute the test; or

cause the computing device, that is remote from the one or more processors, to execute the test.

11. A method, comprising:

receiving, by one or more processing circuits, a request to publish a resource on a digital repository;

presenting, by the one or more processing circuits, via a user interface, an aspect of the request;

receiving, by the one or more processing circuits, via the user interface, an input subsequent to presenting the aspect of the request;

determining, by the one or more processing circuits, based on the input, that a format of the request is valid;

causing, by the one or more processing circuits, responsive to determining that the format of the request is valid, an execution of a test on the request, wherein the test comprises:

converting the request to at least one application programming interface (API) call;

receiving, responsive to transmitting the at least one API call, at least one API response which represents a result of execution of the at least one API call; and

determining, using the at least one API response, a status of the resource; and

sending, by the one or more processing circuits, the status of the resource to a computing device.

12. The method of claim 11 , wherein the at least one API response includes a first format selected based on a backend server successfully implementing a configuration change of the request, and wherein the at least one API response includes a second format selected based on the backend server unsuccessfully implementing the configuration change.

13. The method of claim 11 , further comprising:

generating, by the one or more processing circuits, information associated with a first configuration change of the request;

storing, by the one or more processing circuits, in a database, the information associated with the first configuration change; and

updating, by the one or more processing circuits, responsive to receiving at least one second API response, the information associated with the first configuration change to reflect a second configuration change.

14. The method of claim 11 , wherein the resource includes at least one of:

a uniform resource locator (URL);

a uniform resource identifier (URI);

a service; or

a subscription.

15. The method of claim 11 , wherein the request includes at least one of:

a request to create the resource;

a request to modify the resource;

a request to view the resource;

a request for workflow approval of the resource; or

a request to delete the resource.

16. The method of claim 11 , wherein the at least one API call includes at least one of:

a web service API;

a Firewall API;

a certificate API;

a VIP API; and

a DNS API.

17. The method of claim 11 , wherein the request is received from the computing device, and wherein the request is instantiated by at least one of:

one or more interactions with a web browser presented by the computing device; or

a programmatic API call transmitted by the computing device.

18. The method of claim 11 , wherein the format of the request includes at least one of:

a URL name;

a service name;

a LDAP name;

a server identifier;

a VIP identifier; or

a port number.

19. A non-transitory computer readable storage media having instructions stored thereon that, when executed by one or more processors, cause the one or more processors to implement operations comprising:

receiving a request to publish a resource on a digital repository;

presenting, via a user interface, an aspect of the request;

receiving, via the user interface, an input subsequent to presenting the aspect of the request;

determining, based on the input, that a format of the request is valid;

causing, responsive to determination that the format of the request is valid, an execution of a test on the request, wherein the test comprises:

converting the request to at least one application programming interface (API) call;

receiving, responsive to transmitting the at least one API call, at least one API response which represents a result of execution of the at least one API call; and

determining, using the at least one API response, a status of the resource; and

sending the status of the resource to a computing device.

20. The non-transitory computer readable storage media of claim 19 , the operations further comprising:

receiving, via the input, an indication that the format of the request is valid; and

determining, based on the indication, that the format of the request is valid.

Continuity (3)

References Cited (28)