Authentication token management for multiple processes and representational state transfer clients
Embodiments for processing authentication tokens in a system with multiple Representational State Transfer (REST) servers and clients. An intelligence process for multiple processes or multiple REST clients in an OS effectively communicates with multiple REST servers and proactively manages each server's authentication token. A shared library is loaded into a process that uses shared memory to manage the generation and expiry of a token and to communicate with a supported REST server through a single function call. The REST Authentication token will be generated for each REST server and stored in the shared memory which will be reused across multiple processes that use the library. The REST token will be validated for each function call.
1. A computer-implemented method of authenticating a Representational State Transfer (REST) server for one or more processes in a client-server network, comprising:
allocating a shared memory accessible to multiple clients of the network;
generating a respective server authentication token for each server, the authentication token valid for a period of time defined by an expiration time;
implementing a shared library function that uses the shared memory to manage the generation and expiry of each server authentication token and to communicate with appropriate servers through a single function call initiated by a requesting client; and
reusing, during the period of time, a valid token by later processes accessing the respective server requests to the respective server made by the later processes.
2. The method of claim 1 further comprising validating the valid token in each of the respective server requests made by the later processes.
3. The method of claim 2 further comprising:
returning, after the period of time, a false value in response to a token validation for the respective server; and
generating, for the respective server, a new token in response to a next request for server access by a next process subsequent to the period of time, wherein the new token is valid for an additional period of time.
4. The method of claim 3 wherein next request is different from an initial request generating an initial token.
5. The method of claim 3 further comprising:
building a client uniform resource locator (CURL) data element for the request; and
executing the CURL.
6. The method of claim 5 wherein the network comprises one of: a cloud network provided by a cloud service provider, and the servers are accessed using URL naming conventions, or an on-premises client-server network functioning under a single operating system environment.
7. The method of claim 6 wherein the server supports a network resource accessed by the client, and wherein the network resource comprises at least one of storage, processors, applications, and content.