SYSTEM AND METHOD FOR A TOKEN GATEWAY ENVIRONMENT
Embodiments include a method for providing tokens which includes: receiving from a user system an encrypted data packet including user credentials and a request for an authentication token to access protected resources; extracting the user's security information; transmitting a data packet to a security and access management system, where the data packet includes the user's security information and a request for user validation; receiving, from the security and access management system, user validation and additional data; generating a thin token and a fat token; storing the thin token in association with the fat token; transmitting the thin token to the user system; receiving, from the user system, a request to access protected resources from a protected resource system, the request including the thin token; validating the received thin token; accessing the fat token associated with the thin token; and transmitting the fat token to the protected resource system.
1 - 20 . (canceled)
21 . A system for providing tokens to facilitate authentication and access to protected resources, the system comprising:
a token gateway computing system, wherein the token gateway computing system is configured to:
receive, from a user computing system, a first 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 second data packet to a first access management computing system;
receive, from the first access management computing system, validation of the user, and private data;
generate a first token;
generate a second token using the private data, wherein the second token comprises a first portion of the first token and additional data;
transmit the first token to the user computing system;
receive, from the user computing system, a request to access the one or more protected resources from the protected resource computing system, the request comprising the first token;
validate the received first token; and
transmit the second token to the protected resource computing system.
22 . The system of claim 21 , wherein the first token and the second token are based on a JavaScript Object Notation (JSON) web token standard.
23 . The system of claim 21 , wherein the token gateway computing system is further configured to transmit the second data packet based on a type associated with the one or more protected resources requested.
24 . The system of claim 21 , wherein the first token is a thin token and the second token is a fat token.
25 . The system of claim 21 , wherein the first portion of the first token comprises a payload.
26 . The system of claim 21 , wherein the first token and second token headers each include a public key and a type associated with the token.
27 . The system of claim 21 , wherein the first portion of the first token includes at least a username, an email, a first name, an issuer of the first token, a last name, an expiry time, an issue time, and a unique identifier.
28 . The system of claim 21 , wherein the additional data in the second token include details regarding the protected resources.
29 . The system of claim 28 , wherein the additional data includes:
a product name of a protected resource as identified in the first access management computing system;
product options associated with the product name; and
additional custom information requested by users and administrators of the protected resource computing system.
30 . 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 first 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 second data packet to a first access management computing system;
receiving, from the first access management computing system, validation of the user, and private data;
generating a first token;
generating a second token using the private data, wherein the second token comprises a first portion of the first token and additional data;
transmitting the first token to the user computing system;
receiving, from the user computing system, a request to access the one or more protected resources from the protected resource computing system, the request comprising the first token;
validating the received first token; and
transmitting the second token to the protected resource computing system.
31 . The computer-implemented method of claim 30 , wherein the first token and the second token are based on a JavaScript Object Notation (JSON) web token standard.
32 . The computer-implemented method of claim 30 , wherein the token gateway system is further configured to transmit the second data packet based on a type associated with the one or more protected resources requested.
33 . The computer-implemented method of claim 30 , wherein the first token is a thin token and the second token is a fat token.
34 . The computer-implemented method of claim 30 , wherein the first portion of the first token comprises a payload.
35 . The computer-implemented method of claim 30 , wherein the first token and second token headers each include a public key and a type associated with the token.
36 . The computer-implemented method of claim 30 , wherein the first portion of the first token includes at least a username, an email, a first name, an issuer of the first token, a last name, an expiry time, an issue time, and a unique identifier.
37 . The computer-implemented method of claim 30 , wherein the additional data in the second token include details regarding the protected resources.
38 . The computer-implemented method of claim 37 , wherein the additional data includes:
a product name of a protected resource as identified in the first access management computing system;
product options associated with the product name; and
additional custom information requested by users and administrators of the protected resource computing system.
39 . 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 first 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 second data packet to a first access management computing system;
receive, from the first access management computing system, validation of the user, and private data;
generate a first token;
generate a second token using the private data, wherein the second token comprises a first portion of the first token and additional data;
transmit the first token to the user computing system;
receive, from the user computing system, a request to access the one or more protected resources from the protected resource computing system, the request comprising the first token;
validate the received first token; and
transmit the second token to the protected resource computing system.
40 . The non-transitory computer storage medium of claim 39 , wherein the first token includes a key pointing to the second token.