eSignet
Last updated
Was this helpful?
Last updated
Was this helpful?
The eSignet service is utilized by Inji Wallet for online login and downloading the VC. Users have the ability to log in to any service provider portal that is integrated with eSignet.
The user is required to open the portal integrated with eSignet and utilize the app scanner to scan the QR code.
After successfully scanning the QR code, Inji Wallet will access the API below and transmit the link code.
After successfully completing the offline face authentication and selecting the required and optional information, the two specified APIs are invoked.
The user is currently on the Add new card
screen and chooses the option to Download via eSignet
.
Inji Wallet utilizes the react-native-app-auth
library to authorize and redirect the user to the eSignet user interface. The configuration for redirection is retrieved as part of the issuer's configuration.
Once the user is on the eSignet user interface, they input the necessary information such as a unique ID and OTP (One-time Password). After entering the OTP, the user is redirected back to Inji Wallet in order to generate a key pair and initiate the request to download the credential.
For credential request, refer credential_endpoint attribute in issuer's configuration response.
The link transaction endpoint is invoked from Wallet-app.
Validates the link-code and its expiry and generates the linkTransactionId. This linkTransactionId is linked to transactionId returned from /oauth-details endpoint.
Returns the auth-factors, clientName, logoUrl, User claims, authorize scopes along with linkTransactionId.
Note: Wallet-app will hereafter address the transaction with this linkTransactionId for the /authenticate and /consent endpoints.
/linked-authorization/link-transaction
Once end user provides the user identifier (UIN/VID) and all the required auth challenge to the Wallet-app, this endpoint will be invoked from wallet-app.
Supported auth-challenge depends on the integrated authentication server.
On Authentication Success: Only linkTransactionId is returned in the below response without any errors.
On Authentication Failure: Error list will be set with the errors returned from the integrated authentication server.
/linked-authorization/authenticate
yyyy-MM-dd'T'HH:mm:ss.SSS'Z'
Once the authentication is successful and user consent is obtained, this endpoint will be invoked by the wallet app to send the accepted consent and permitted scopes.
/linked-authorization/consent
yyyy-MM-dd'T'HH:mm:ss.SSS'Z'
Once the access token is received via the token endpoint, Wallet should invoke this endpoint to get the verifiable credential.
/vci/credential
Format of the Credential to be issued.
ldp_vc
, jwt_vc_json
, jwt_vc_json-ld
JSON object containing proof of possession of the key material the issued Credential shall be bound to.
JSON object containing (and isolating) the detailed description of the credential type. * This object MUST be processed using full JSON-LD processing. If it consists of the following sub claims: * @context: REQUIRED. JSON array