Accepting Authorization Result

Learn how to accept the response of authorization

Verifiable Credential Verification

Once redirected to SSO, the end-user will experience the following:

• A QR code will be shown to scan with his mobile wallet. Scanning the code will initiate a verification process with the verifier API.

• After presenting the requested credentials, the browser will redirect the end-user back to your service, to the callback URL your service provided.

---

Redirect Response

If the credential verification process was successful, the client will receive an authorization code and state as query parameters in the redirect URI as specified in the OAuth v2 spec. Parameters will be encoded in the query component of the URI using the application/x-www-form-urlencoded formatting. In case of an error, the callback URI will contain the error code and a simple description message.

Example redirect URIs:

success:

https://your-domain.com/oauth/callback?code=SplxlOBeZQQYbYS6WxSbIA&state=96f97c93-599d-4e0a-a87e-116c10d399b5

error:

https://your-domain.com/oauth/callback?error=server_error&error_description=why&state=96f97c93-599d-4e0a-a87e-116c10d399b5

Attributes

---

code, string

the authorization code for the client service to access user data

---

state, string

the value your client service provided at authorization request used to correlate requests and prevent certain types of attacks

---

error, enum

Error code idicating type of error. One of OAuth v2 error codes

---

error_description, string

A human readable description of the error