Introducing VIDA Identity Stack: All of VIDA, in one place 🎉
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Password - Completion

Provisioning Completion API

The Password Provisioning Completion API serves as the second step in the password provisioning process. The user submits the password they have chosen, along with any required information, to the server. Upon successful verification, the server responds with a JSON Web Token (JWT) containing the newly provisioned credential ID.

API Description

Method : POST

URL : Follow up url received as part of the response of the Transaction Initiation API

Parameters

Name
Type
Description

client_id*

String

A unique client id that is shared for each partner.

password*

String

password to be used for the authentication

Headers

Name
Type
Description

Authorization*

String

Bearer {Bearer Token Received in Transaction Initiation API}

Content-Type

String

application/x-www-form-urlencoded

{
    "entity": {
        "accessToken": "eyJhbGciOiJSUzI1NiIsInR5cCIgOiAiSldUIiwia2lkIiA6ICJYbnNBNFVPdlkyU0JLSkdnX1ppTHN1Tk8tZ2dlLVB0RXZzX2twRTBhd3RnIn0.eyJleHAiOjE3MDMwNjI3OTIsIm5iZiI6MTcwMzA2MjQ5MiwiaWF0IjoxNzAzMDYyNDkyLCJhdXRoX3RpbWUiOjE3MDMwNjI0OTIsImp0aSI6IjVmZDVjMTRiLTFlNzQtNGE5NS1iZDZhLTA4YWZmOWIxYzNhNCIsImlzcyI6Imh0dHBzOi8va2V5Y2xvYWsuYXV0aC1zdGFnZS52aWRhLmlkL3JlYWxtcy9zcHJpbmdib290LXF1aWNrc3RhcnQiLCJzdWIiOiJkMmIzYjc4Yi0yYmE1LTQ0MjAtYTZmOC02MDFhODJhNGVmYjQiLCJ0eXAiOiJCZWFyZXIiLCJhenAiOiJhcGkiLCJzZXNzaW9uX3N0YXRlIjoiNTRlYzQ0YzAtODQ5NS00MjEwLTljZDktMzhkNmQwMDQ4Yzg3Iiwic2NvcGUiOiIiLCJzaWQiOiI1NGVjNDRjMC04NDk1LTQyMTAtOWNkOS0zOGQ2ZDAwNDhjODciLCJzZXNzaW9uX2lkZW50aWZpZXIiOiJEeWhHZktGRHF5ayIsInR5cGUiOiJwYXNzd29yZCIsImNyZWRlbnRpYWxfaWQiOiI5Zjk1NGEyYi1mMDEwLTRhZWUtODE3MC0zODhiYjMwZTBlODgifQ.Il6wv47FF2ToovYx-4zXCxTyyCn006ZAXLvzSFcvxXsuBdoFDrajDkoWpd-OUS7ks2tvevNh1-Zz4JoZigfHVOjuMPHQma7tkeqdZ-nyhoiFqDyVxggykLsJyNZNrZoIUn3ROT42Qidp-b2nABSpzWqgEg_FclSbb5Fgdqy9v7F3Inq03Cu4qNxAdNOAm9Ekt-PqPB73RYUePaBok3mfJROzqKgAUAfbEr7YJaa-PdqGeubh3Cg2UQbkBgkvPdvN47fww7D3V4NtKvtdTZOq9nAwLbbcCh5dtZwf4jQ3o7En2nmGeL5C5LBFPI6dnOgjFcQM3-BPE6nONVl4tCXH3w",
        "accessExpiresIn": 300,
        "refreshToken": "eyJhbGciOiJIUzI1NiIsInR5cCIgOiAiSldUIiwia2lkIiA6ICJmMjFhZGYyZS03NWU2LTQ5Y2UtOWYwZi00ZDEwNjE0MDA4NGEifQ.eyJleHAiOjE3MDMwNjQyOTIsImlhdCI6MTcwMzA2MjQ5MiwianRpIjoiNmM4YjYzOTMtMmNjNC00MDZhLTg2NzktM2IwNWVjY2RkMDA2IiwiaXNzIjoiaHR0cHM6Ly9rZXljbG9hay5hdXRoLXN0YWdlLnZpZGEuaWQvcmVhbG1zL3NwcmluZ2Jvb3QtcXVpY2tzdGFydCIsImF1ZCI6Imh0dHBzOi8va2V5Y2xvYWsuYXV0aC1zdGFnZS52aWRhLmlkL3JlYWxtcy9zcHJpbmdib290LXF1aWNrc3RhcnQiLCJzdWIiOiJkMmIzYjc4Yi0yYmE1LTQ0MjAtYTZmOC02MDFhODJhNGVmYjQiLCJ0eXAiOiJSZWZyZXNoIiwiYXpwIjoiYXBpIiwic2Vzc2lvbl9zdGF0ZSI6IjU0ZWM0NGMwLTg0OTUtNDIxMC05Y2Q5LTM4ZDZkMDA0OGM4NyIsInNjb3BlIjoiIiwic2lkIjoiNTRlYzQ0YzAtODQ5NS00MjEwLTljZDktMzhkNmQwMDQ4Yzg3In0.xIZOQKLso47dD-g1-t4n2gxs8zqW40LLDsNyLnkOrso",
        "refreshExpiresIn": 1800,
        "authType": "password"
    },
    "uri": "https://{environment-url}/realms/{partner-id}/protocol/api/required-action",
    "bearerToken": "eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJzdWIiOiI1NGVjNDRjMC04NDk1LTQyMTAtOWNkOS0zOGQ2ZDAwNDhjODciLCJleGVjdXRpb24iOiJ2aWRhLXBhc3N3b3JkLXJlZ2lzdGVyIiwidGFiX2lkIjoiRHloR2ZLRkRxeWsiLCJuYmYiOjE3MDMwNjI0OTIsInNlc3Npb25fY29kZSI6InRrWFJkQmJ4UE1UYVcyRk9laGo2VVVVVk5oYWhma2RTOXltWE1ZMExxbGsiLCJzZXNzaW9uX2lkZW50aWZpZXIiOiJEeWhHZktGRHF5ayIsImV4cCI6MTcwMzA2Mjc5MiwiaWF0IjoxNzAzMDYyNDkyLCJhdXRoX3Nlc3Npb25faWQiOiI1NGVjNDRjMC04NDk1LTQyMTAtOWNkOS0zOGQ2ZDAwNDhjODciLCJqdGkiOiI2N2IzYjIyYy0yODM0LTQ4OWYtYmUwYi1hNzM5Yjg4MDMwNWEifQ.466-r_jCinFdkvz_blqAGQFLS08Vpxu0B9uqicq_NRI",
    "authType": "password"
}

Success Response

Error Response

Response Schema

For a complete list of error codes and their meanings, refer to the Error Scenarios section.

Password Authentication Completion API

The Password Authentication API is used for completing the user authentication process for a transaction. After initiating a request for authentication, the server responds with a session ID, bearer token, and a challenge. To finalize the transaction, the user responds to this challenge by submitting the password they have chosen. The API then validates this password against the credential stored during the provisioning phase.

API Description

Method : POST

URL : Follow up url received as part of the response of the Transaction Initiation API

Parameters

Name
Type
Description

client_id*

String

A unique client id that is shared for each partner.

password

String

Password to be used for the authentication

Headers

Name
Type
Description

Authorization

String

Bearer {Bearer Token Received in Transaction Initiation API}

Content-Type

String

application/x-www-form-urlencoded

Success Response

Error Response

Response Schema

For a complete list of error codes and their meanings, refer to the Error Scenarios section.

Last updated