Digital identity system
A method of a digital identity system generating a sharing token for authenticating a bearer to a validator, wherein a data store of the digital identity system holds a plurality of attributes of the bearer, the method comprising implementing by the digital identity system the following steps: receiving at the digital identity system from a bearer an electronic sharing token request, wherein the token request identifies at least one of the bearer's attributes in the data store selected for sharing with a validator; in response to the electronic token request, generating a sharing token, which is unique to that request, for presentation by the bearer to a validator; associating with the unique sharing token at the digital identity system the identified at least one bearer attribute; and issuing to the bearer the unique sharing token; and wherein later presentation of the unique sharing token to the digital identify system by a validator causes the at least one bearer attribute associated with the sharing token to be rendered available to the validator by the digital identity system.
1. A digital identity system comprising:
a network interface configured to send and receive electronic messages; and
at least one hardware processor configured to perform operations comprising:
receiving in a message, from a device of an authoring party, a data item of a user with a credential of the user, wherein the user is not the authoring party;
validating the credential, and when the credential is valid, creating an assigned profile for the user, the assigned profile comprising the data item; and
issuing, to a device of the user, a token bound to the assigned profile, wherein presentation of the token to the digital identity system causes the assigned profile to be rendered available to a presenting entity.
2. The digital identity system of claim 1 , wherein the at least one hardware processor of the digital identity system is configured to enable the authoring party to modify or cancel the assigned profile.
3. The digital identity system of claim 1 , wherein details of the authoring party are provided to the presenting entity.
4. The digital identity system according to claim 1 , wherein the operations further comprise generating the credential of the user for providing to the authoring party device.
5. The digital identity system according to claim 4 , wherein the operations further comprise rendering available, to the authoring party, identity data of the user.
6. The digital identity system according to claim 4 , wherein each of the user and the authoring party is associated with a respective code unique to that entity, wherein the operations further comprise generating and rendering available, to the authoring party, a unique composite code, by combining the code of the user with the code of the authoring party, wherein neither of the codes is derivable from the composite code alone.
7. The digital identity system of claim 1 , wherein the operations further comprise issuing the token in response to an electronic sharing token request received from the user device, the assigned profile in the form of one or more attributes selected at the user device when requesting the sharing token.
8. The digital identity system of claim 1 , wherein the token is associated with a visual image of the user that is rendered available to the presenting entity when the token is presented.
9. The digital identity system of claim 1 , wherein the message received from the device of the authoring party further comprises a credential of the authoring party, wherein the operations further comprise:
validating the credential of the authoring party, and creating the assigned profile of the user when both the credential of the authoring party and the credential of the user are valid.
10. The digital identity system of claim 9 , wherein the operations further comprise determining authorizations attached to the credential of the authoring party, and confirming that the authoring party is allowed to assign profiles to users of the digital identity system.
11. The digital identity system according to claim 1 , wherein the assigned profile contains medical information.
12. The system of claim 1 , wherein the device of the user includes executable code that, when executed by a hardware processor of the device of the user, causes the device of the user to display the token as a barcode or QR code.
13. A system comprising:
a digital identity system comprising:
a network interface configured to send and receive electronic messages; and
at least one hardware processor configured to perform operations comprising:
receiving in a message, from a device of an authoring party, a data item of a user with a credential of the user, wherein the user is not the authoring party;
validating the credential, and when the credential is valid, creating an assigned profile for the user, the assigned profile comprising the data item; and
issuing, to a device of the user, a token bound to the assigned profile, wherein presentation of the token to the digital identity system causes the assigned profile to be rendered available to a presenting entity; and
said device of the user, wherein the device of the user includes executable code that, when executed by a hardware processor of the device of the user, causes the device of the user to: cause the credential of the user to be rendered available to the authoring party, receive the token from the digital identity system, and display the token on a display of the user device for capturing by the presenting entity.
14. One or more non-transitory computer readable storage medium embodying executable instructions then, when executed on a hardware processor of a digital identity system, cause the digital identity system to perform operations of:
receiving in a message, from a device of an authoring party, a data item of a user with a credential of the user, wherein the user is not the authoring party;
validating the credential, and when the credential is valid, creating an assigned profile for the user, the assigned profile comprising the data item; and
issuing, to a device of the user, a token bound to the assigned profile, wherein presentation of the token to the digital identity system causes the assigned profile to be rendered available to a presenting entity.
15. The one or more non-transitory computer readable storage medium of claim 14 , wherein the operations further comprise enabling the authoring party to modify or cancel the assigned profile.
16. The one or more non-transitory computer readable storage medium of claim 14 , wherein the operations further comprise generating the credential of the user for providing to the authoring party device.
17. The one or more non-transitory computer readable storage medium of claim 16 , wherein the operations further comprise rendering available, to the authoring party, identity data of the user.
18. The one or more non-transitory computer readable storage medium of claim 16 , wherein each of the user and the authoring party is associated with a respective code unique to that entity, wherein the operations further comprise generating and rendering available, to the authoring party, a unique composite code, by combining the code of the user with the code of the authoring party, and wherein neither of the codes is derivable from the composite code alone.
19. The one or more non-transitory computer readable storage medium of claim 14 , wherein the operations further comprise issuing the token in response to an electronic sharing token request received from the user device, the assigned profile in the form of one or more attributes selected at the user device when requesting the sharing token.
20. The one or more non-transitory computer readable storage medium of claim 14 , wherein the message received from the device of the authoring party further comprises a credential of the authoring party, and wherein the operations further comprise validating the credential of the authoring party, and creating the assigned profile of the user when both the credential of the authoring party and the credential of the user are valid.