...
A user-friendly and customisable mechanism should be in place to facilitate integration with credential issuers. This ensures a simplified and efficient addition of new credentials to the wallet.
| Tip |
|---|
Use Case Robert is applying applies for a health insurance at with XYZ Insurance. The administrators at Upon verifying his details, XYZ Insurance , after verifying the details shared by Robert and issue a policy over email. In the email, the issuer, XYZ Insurance, shares issues the policy and sends it to Robert via email. The email contains a QR code. When Robert scans the QR code using with his mobile phone, which opens up the wallet (if the wallet is available on the phone) and asks Robert the wallet app prompts him to enter the policy ID and date of birth for security reasons. Robert after Upon entering the details, Robert receives the Policy Credential on in the wallet. |
| Info |
|---|
|
1.2. Secure Storage of Credentials in Wallet
...
Ordering of credentials in the wallet
Ability to categorise the credentials based on type
Ability to give a name to the credential
1.4. Remove a Credential from the Wallet
The wallet must allow the holder the ability to remove credentials from the wallet.
| Tip |
|---|
Use Case Moris plans a trip to the Caribbean, purchases flight tickets, and adds the ticket credentials to his wallet. However, due to unforeseen circumstances, he has to cancel the trip. To tidy up his wallet, he decides to remove the ticket credentials:
|
1.5. Transfer of Credentials from One Device to Another
The credentials can be transfered from one device to another (when credentials are locally stored in a device) by the holder. The transfer can happen subject to the binding of credentials to the new device has to happen once again.
| Tip |
|---|
Use Case Amanda is , in the process of upgrading her phone. She wants , needs to transfer all her data from the old phone to the new phone. She also wanted to transfer all her credentials documents to her new phone (assuming there is no cloud wallet which could do this automatically). She sees an options in settings screen of the wallet stating “Transfer to new device” and “Transfer from another device”.She installs the wallet in her new phone and clicks on the on the option “Transfer from another device”, a QR code opens which has the connection details. The she clicks on the option “Transfer to new device”, a QR code scanner opens and she uses it to scan the QR code on her new phone. A connection is established between both the phones and in her old phone, Amanda, sees her list of credentials pre-selected and has a button called “Authenticate & Share” and/or “Share“ (based on the security level added by the issuer). She clicks on the button and authenticates her self and all her credentials are transfered to the new phone, including credentials and documents, to her new device. With no automatic cloud wallet integration available, she follows these steps:
|
2. Presentation and Sharing of Credentials
...
To enhance privacy, the holder should be able to choose and share specific attributes of a credential without revealing unnecessary details, giving them control over the information disclosed.
| Tip |
|---|
Hari, a 19-year-old, was riding his bike when he was stopped by a Traffic Police officer. Observing Hari's youthful appearance, the officer decided to verify Hari's age since the country has a minimum age limit of 18 for individuals to ride a vehicle. The officer requested Hari to show his credentials for age verification. In response, Hari accessed his mobile wallet, while the police officer opened his verification application. The officer then initiated an authorization request to Hari's device. Hari's wallet retrieved the request object, which requested for the claim "ageOver18" from his driving license to be shared. The wallet informed Hari that the Police Officer was seeking confirmation of whether the age is over 18 or not. Considering that his driving license credential contained the claim "ageOver18," Hari authorized the sharing of this information with the police officer. |
| Info |
|---|
Reference:
|
| Info |
|---|
Selective Disclosure Signatures |
2.3. Mode of Sharing
The wallet should provide a mechanism for the holder to share the credentials in a secure and standardised manner using standard protocols.
...
5. Administation
5.1. Governance
The importance of this
5.1.1. Creation of a Wallet Registry
In the context of the system's administration and governance in a country, the creation of a Wallet Registry could be needed. This registry serves the purpose of recording and managing wallets authorized to store credentials that are issued within the country. The primary objective is to establish a controlled environment where issuers can verify the authenticity of a wallet before transferring or sharing credentials to it.
5.1.2. Creation of a Sectorial Issuer Registry
In the governance framework of the system, a Sectorial Issuer Registry can be established. This registry is intended to systematically record and manage information about issuers operating within specific sectors. The goal is to provide a structured approach for overseeing and verifying the legitimacy of issuers before they participate in the issuance and sharing of credentials. This registry can be used by wallets or verifiers to verify by the
5.1.3. Workflow Management for Registration
Should provide a configurable workflow to perform review of the application shared by a wallet solution or Issuer to register into the respective trust registry.
5.2. Issuer Side Administrator
5.
...
2.1. Issuance of Credentials into Registry
Should be able to register a credentials
Should be able to
...
As part of the administrative capabilities on the issuer side, the Issuer Side Administrator should have the functionality to add credentials into the registry.
5.2.2. Revocation of Issued Credential
...
Should be able to revoke a credential
...
The system should facilitate the revocation and potential reversal of issued credentials by administrators.
5.
...
2.3. Ledger Management
...
Issuer Side Administrators should have the capability to trace
...
and monitor changes made
...
to a credential using a ledger.
5.
...
2.4. Controls by Issuers
The format of the credential to be Issued
The type of the credential to be issued
The authentication methods for issuing a credential
The authentication methods to share a credential from a wallet
...
6.
...
Wallet Usage
This section will detail the usage of wallet once the credentials are onboarded on the wallet.
6.1. Credentials for Authentication
This feature allows credential holders to authenticate themselves using selected credentials stored in the wallet, leveraging diverse authentication mechanisms available within the wallet's functionality.
5.1. Authentication Methods
The wallet should be able to support multiple authentication methods, including but not limited to biometrics (fingerprint, facial recognition), PIN, and passphrase. This would enable the holder to have the flexibility to choose and configure their preferred authentication method.
5.2. Secure Authentication Protocols
The wallet should have robust and secure authentication protocols, ensuring the confidentiality and integrity of authentication processes. Industry-standard protocols such as OAuth or OpenID Connect should be used for secure interactions.The type of authentication methods supported by a credential can be defined by the issuer.
6.2. Using Wallet for Signing Documents
This feature allows the user to take a document as input and sign it using the user’s key present in the user’s device which is bounded to a specific credential.
6.2. Using Wallet for storing and sharing Documents
The user can use his wallet like a Personal Vault.
This feature allows the user to save and share personals documents (eg passport, birth certificate, diploma,…)