Digital identity
Disclosed herein is an identity network that can provide a universal, digital identity for users that can be used to authenticate the user by an identity provider for relying parties. The identity network receives a request from a relying party that includes deep linking to an identity provider selected by the user. The request specifies the user as well as any other information about the user the relying party is requesting. A service of the identity network launches the application for the identity provider on the user's device using a software development kit. The user can log into the identity provider's application, which validates the user and provides the user authentication/validation and information about the user to the identity network. The identity network can then provide the indication of the user's authentication and the user information to the relying party.
1. A method for using an authenticated, universal digital identity for a user, the method comprising:
receiving, by a relying party, a first request from a user to sign up for access to the relying party using a digital identity of the user;
providing, by the relying party, one or more identity providers for the user to select from;
receiving, by the relying party, a selection from the user of a specific identity provider from the one or more identity providers;
submitting, by the relying party, a second request to an identity network to retrieve identity attributes from the specific identity provider;
receiving, by the relying party, the identity attributes from the identity network, the identity attributes originating from the specific identity provider, wherein the identity attributes are encrypted using a first encryption key;
receiving a second encryption key from the specific identity provider that is used to decrypt the identity attributes; and
providing the second encryption key to the identity network prior to receiving the identity attributes.
2. The method for using an authenticated, universal digital identity for a user of claim 1 , further comprising:
populating, by the relying party, one or more user information fields of a relying party application form of the relying party with the identity attributes.
3. The method for using an authenticated, universal digital identity for a user of claim 1 , wherein:
the method further comprises decrypting, by the relying party, the identity attributes.
4. The method for using an authenticated, universal digital identity for a user of claim 3 , wherein:
the identity attributes comprise additional information from a third party;
the identity attributes and the additional information are encrypted using an additional key; and
the method further comprises decrypting, by the relying party, the identity attributes and the additional information.
5. The method for using an authenticated, universal digital identity for a user of claim 1 , wherein:
the identity attributes comprise at least one attribute selected from a group consisting of a name of the user, a residential address of the user, an email address of the user, a telephone number of the user, and credit score of the user.
6. A relying party, comprising:
one or more processors; and
a memory having stored thereon instructions that, upon execution by the one or more processors, cause the one or more processors to:
receive a first request from a user to sign up for access to the relying party using a digital identity of the user;
provide one or more identity providers for the user to select from;
receive a selection from the user of a specific identity provider from the one or more identity providers;
submit a second request to an identity network to retrieve identity attributes from the specific identity provider; and
receive the identity attributes from the identity network, the identity attributes originating from the specific identity provider, wherein the identity attributes are encrypted using a first encryption key;
receive a second encryption key from the specific identity provider that is used to decrypt the identity attributes; and
provide the second encryption key to the identity network prior to receiving the identity attributes.
7. The relying party of claim 6 , wherein the instructions further cause the one or more processors to:
enroll in a digital identity program of the identity network.
8. The relying party of claim 7 , wherein:
enrolling in the digital identity program comprises integrating a software development kit provided by the identity network into a mobile application of the relying party.
9. The relying party of claim 6 , wherein the instructions further cause the one or more processors to:
identify a token associated with the user for the specific identity provider; and
use the token to identify the specific identity provider.
10. The relying party of claim 9 , wherein:
the token is received from the user with the selection of the specific identity provider, the token is received from the specific identity provider, or the token is received from the identity network.
11. The relying party of claim 6 , wherein the instructions further cause the one or more processors to:
populate one or more user information fields of a relying party application form of the relying party with the identity attributes.
12. The relying party of claim 6 , wherein:
the instructions further cause the one or more processors to decrypt the identity attributes.
13. A non-transitory computer-readable medium having instructions stored thereon that, upon execution by one or more processors of a relying party, cause the one or more processors to:
receive a first request from a user to sign up for access to the relying party using a digital identity of the user;
provide one or more identity providers for the user to select from;
receive a selection from the user of a specific identity provider from the one or more identity providers;
submit a second request to an identity network to retrieve identity attributes from the specific identity provider; and
receive the identity attributes from the identity network, the identity attributes originating from the specific identity provider, wherein the identity attributes are encrypted using a first encryption key;
receive a second encryption key from the specific identity provider that is used to decrypt the identity attributes; and
provide the second encryption key to the identity network prior to receiving the identity attributes.
14. The non-transitory computer-readable medium of claim 13 , wherein the instructions further cause the one or more processors to:
populate one or more user information fields of a relying party application form of the relying party with the identity attributes.
15. The non-transitory computer-readable medium of claim 13 , wherein:
the instructions further cause the one or more processors to decrypt the identity attributes.
16. The non-transitory computer-readable medium of claim 15 , wherein:
the identity attributes comprise additional information from a third party;
the identity attributes and the additional information are encrypted using an additional key; and
the instructions further cause the one or more processors to decrypt the identity attributes and the additional information.
17. The non-transitory computer-readable medium of claim 13 , wherein the instructions further cause the one or more processors to:
identify a token associated with the user for the specific identity provider; and
use the token to identify the specific identity provider.