Workflow
Understanding the workflow:
The identity owner initiates a credential request by accessing the landing page.
Upon request, the user is directed to the authentication page, managed by a backend implementing OpenID Connect.
The user provides personally identifiable information (PII) to eSignet, which is verified against the identity registry.
An authentication code, valid for a single use, is provided to the third-party web service, facilitating token retrieval.
Upon successful verification of the access token, the credential is issued to the identity holder.
Note: To understand the Inji Certify components in detail please refer to the topic Components under Technical Overview section.
Last updated