System and method for a token gateway environment

1. A system for providing tokens to facilitate authentication and access to protected resources, the system comprising:

a token gateway computing system in electronic communication with a user computing system; at least one security and access management computing system; a token management computing system; and a protected resource computing system,

wherein the token gateway computing system is configured to:

receive, from the user computing system, a data packet including user credentials of a user and a request for an authentication token to access one or more protected resources from the protected resource computing system;

transmit a validation request to the at least one security and access management computing system based on a type associated with the one or more protected resources requested;

receive, from the at least one security and access management computing system, validation of the user, and private data;

generate a thin token;

generate a fat token using the private data;

store the thin token in association with the fat token in the token management computing system;

transmit the thin token to the user computing system;

receive, from the user computing system, a request to access one or more protected resources from the protected resource computing system, the request comprising the thin token;

validate the received thin token;

access the fat token associated with the thin token in the token management computing system; and

transmit the fat token to the protected resource computing system,

wherein the thin token and the fat token are based on a JavaScript Object Notation (JSON) web token standard;

wherein a thin token payload includes at least an indication of an issuer of the token, an issue time, and a unique identifier; and

wherein a fat token payload comprises the thin token payload and additional data.

2. The system of claim 1 , wherein the thin token and fat token headers each include a digital signature, a public key, and a type associated with the token.

3. The system of claim 1 , wherein the additional data in the fat token payload include details regarding the protected resources.

4. The system of claim 3 , wherein the additional data includes:

a product name of a protected resource as identified in the at least one security and access management platform;

product options associated with the product name; and

additional custom information requested by users and administrators of the protected resource computing system.

5. The system of claim 1 , wherein the token gateway computing system is further configured to:

receive, from the user computing system, a request for a refreshed thin token;

validate a header within the request;

generate a refreshed thin token;

store the refreshed token in association with the previously generated thin token; and

send the refreshed token back to the user computing system.

6. The system of claim 5 , wherein the previously generated thin token includes an expiry date, and wherein the refreshed token includes a different expiry date than the expiry date of the previously generated thin token.

7. The system of claim 1 , wherein the token gateway computing system is further configured to:

receive, from the user computing system, a request for revoking the thin token;

validate a header within the request;

revoke the thin token; and

alter the stored version of the previously generated thin token.

8. A computer-implemented method for providing tokens to facilitate authentication and access to protected resources, the computer-implemented method comprising, as implemented by one or more computing devices within a token gateway system configured with specific executable instructions:

receiving, from a user computing system, a data packet including user credentials of a user and a request for an authentication token to access one or more protected resources from a protected resource computing system;

transmitting a validation request to at least one security and access management computing system based on a type associated with the one or more protected resources requested;

receiving, from the at least one security and access management computing system, validation of the user, and private data;

generating a thin token;

generating a fat token using the private data;

storing the thin token in association with the fat token in the token management computing system;

transmitting the thin token to the user computing system;

receiving, from the user computing system, a request to access one or more protected resources from the protected resource computing system, the request comprising the thin token;

validating the received thin token;

accessing the fat token associated with the thin token in a token management computing system; and

transmitting the fat token to the protected resource computing system,

wherein the thin token and the fat token are based on a JavaScript Object Notation (JSON) web token standard;

wherein a thin token payload includes at least an indication of an issuer of the token, an issue time, and a unique identifier; and

wherein a fat token payload comprises the thin token payload and additional data.

9. The computer-implemented method of claim 8 , wherein the thin token and fat token headers each include a digital signature, a public key, and a type associated with the token.

10. The computer-implemented method of claim 8 , wherein the additional data in the fat token payload include details regarding the protected resources.

11. The computer-implemented method of claim 10 , wherein the additional data includes:

a product name of a protected resource as identified in the at least one security and access management platform;

product options associated with the product name; and

additional custom information requested by users and administrators of the protected resource computing system.

12. The computer-implemented method of claim 8 further comprising:

receiving, from the user computing system, a request for a refreshed thin token;

validating a header within the request;

generating a refreshed thin token;

storing the refreshed token in association with the previously generated thin token; and

sending the refreshed token back to the user computing system.

13. The method of claim 12 , wherein the previously generated thin token includes an expiry date, and wherein the refreshed token includes a different expiry date than the expiry date of the previously generated thin token.

14. The method of claim 8 , further comprising:

receiving, from the user computing system, a request for revoking the thin token;

validating a header within the request;

revoking the thin token; and

altering the stored version of the previously generated thin token.

15. A non-transitory computer storage medium storing computer-executable instructions that, when executed by a processor, cause the processor to at least:

receive, from a user computing system, a data packet including user credentials of a user and a request for an authentication token to access one or more protected resources from a protected resource computing system;

transmit a validation request to at least one security and access management computing system based on a type associated with the one or more protected resource requested;

receive, from the at least one security and access management computing system, validation of the user, and private data;

generate a thin token;

generate a fat token using the private data;

store the thin token in association with the fat token in the token management computing system;

transmit the thin token to the user computing system;

receive, from the user computing system, a request to access one or more protected resources from the protected resource computing system, the request comprising the thin token;

validate the received thin token;

access the fat token associated with the thin token in a token management computing system; and

transmit the fat token to the protected resource computing system,

wherein the thin token and the fat token are based on a JavaScript Object Notation (JSON) web token standard;

wherein a thin token payload includes at least an indication of an issuer of the token, an issue time, and a unique identifier; and

wherein a fat token payload comprises the thin token payload and additional data.

16. The non-transitory computer storage medium of claim 15 , wherein the thin token includes a key pointing to the fat token.

17. The non-transitory computer storage medium of claim 15 , wherein the computer-executable instructions, when executed by the processor, cause the processor to additionally:

receive, from the user computing system, a request for a refreshed thin token;

validate a header within the request;

generate the refreshed thin token;

store the refreshed token in association with the previously generated thin token; and

send the refreshed token back to the user computing system.

18. The non-transitory computer storage medium of claim 17 , wherein the previously generated thin token includes an expiry date.

19. The non-transitory computer storage medium of claim 18 , wherein the refreshed token includes a different expiry date than the expiry date of the previously generated thin token.

20. The non-transitory computer storage medium of claim 15 , wherein the computer-executable instructions, when executed by the processor, cause the processor to additionally:

receive, from the user computing system, a request for revoking the thin token;

validate a header within the request;

revoke the thin token; and

alter the stored version of the previously generated thin token.