Support for concurrent identities in an identity management solution
An apparatus can include an interface for receiving authentication tokens from a user. The apparatus can include processing circuitry coupled to the interface. The processing circuitry can receive, over the interface, a first authentication token of the user and at least a second authentication token of the user. The processing circuitry can determine whether the first authentication token and at least the second authentication token correspond to an identity associated with the user. The processing circuitry can validate a computing session responsive to determining that the first authentication token and at least the second authentication token can be linked to the identity. Other methods and systems are described.
1. An apparatus including:
an interface for receiving authentication tokens from a user; and
processing circuitry coupled to the interface, the processing circuitry configured to:
receive, over the interface, a first authentication token of the user and at least a second authentication token of the user;
determine whether the first authentication token and at least the second authentication token correspond to an identity associated with the user; and
validate a computing session responsive to determining that the first authentication token and at least the second authentication token can be linked to the identity.
2. The apparatus of claim 1 , wherein the processing circuitry is configured to set a trust level for the user subsequent to the validating.
3. The apparatus of claim 2 , wherein the processing circuitry is configured to increase the trust level for the user responsive to receiving additional authentication tokens.
4. The apparatus of claim 1 , wherein the first authentication token and at least the second authentication token correspond to authentication information for identity management systems.
5. The apparatus of claim 4 , wherein the processing circuitry is configured to detect a type of the identity management systems and to perform validation based on the type.
6. The apparatus of claim 5 , wherein the first authentication token is one of Open Authorization (OAuth) token, a Kerberos ticket, a Security Assertion Markup Language (SAML) assertion, and an Azure token.
7. The apparatus of claim 6 , wherein the second authentication token is of a different type than the first authentication token.
8. The apparatus of claim 6 , wherein the second authentication token is of a same type as the first authentication token.
9. The apparatus of claim 8 , wherein the second authentication token corresponds to a different account of the user than the first authentication token.
10. The apparatus of claim 1 , wherein the processing circuitry is configured to detect whether at least one of first authentication token and the second authentication token is expired and to re-validate responsive to detecting that at least one of the first authentication token and the second authentication token is expired.
11. The apparatus of claim 10 , wherein expiration is determined based on a security level of an application associated with at least one of first authentication token and the second authentication token.
12. The apparatus of claim 1 , wherein the processing circuitry is further configured to generate a primary token subsequent to validating the computing session.
13. The apparatus of claim 12 , wherein the primary token comprises an aggregation of the first authentication token and at least the second authentication token.
14. A computer-readable medium including instructions that, when executed on processing circuitry cause the processing circuitry to perform operations including:
receiving a first authentication token of a user and at least a second authentication token of the user;
determining whether the first authentication token and at least the second authentication token correspond to an identity associated with the user; and
validating a computing session responsive to determining that the first authentication token and at least the second authentication token can be linked to the identity.
15. The computer-readable medium of claim 14 , wherein the operations further include:
setting a trust level for the user subsequent to the validating; and
increasing the trust level for the user responsive to receiving additional authentication tokens.
16. The computer-readable medium of claim 14 , wherein the first authentication token and at least the second authentication token correspond to authentication information for identity management systems, and wherein the operations further include:
detecting a type of the identity management systems; and
performing validation based on the type.
17. The computer-readable medium of claim 16 , wherein the first authentication token is one of Open Authorization (OAuth) token, a Kerberos ticket, a Security Assertion Markup Language (SAML) assertion, and an Azure token.
18. The computer-readable medium of claim 14 , wherein the operations further include:
detecting whether at least one of first authentication token and the second authentication token is expired; and
re-validating responsive to detecting that at least one of the first authentication token and the second authentication token is expired.
19. A method comprising:
receiving a first authentication token of a user and at least a second authentication token of the user;
determining whether the first authentication token and at least the second authentication token correspond to an identity associated with the user; and
validating a computing session responsive to determining that the first authentication token and at least the second authentication token can be linked to the identity.
20. The method of claim 19 , further comprising:
setting a trust level for the user subsequent to the validating; and
increasing the trust level for the user responsive to receiving additional authentication tokens.