AusweisIDent web-flow mock

This service stands in for the Governikus AusweisIDent web-flow so the eID flow can run without a real eID card or the AusweisApp. During an eID identification the product redirects the browser here, and the mock plays back a chosen result.

How the flow works

1. The backend sends the browser to /realms/{realm}/protocol/openid-connect/auth (the QR target).
2. That redirects to the tc-token step, which shows the mock AusweisApp page and continues to the backend callback with a result.
3. The backend exchanges the code at /realms/{realm}/protocol/openid-connect/token and reads the profile at /realms/{realm}/protocol/openid-connect/userinfo.

Approved cards

The result card is selected with the code parameter. The default is Hans.

• Hans
• Andre
• Erika

Declined / error scenarios

Pass an error instead of a card to simulate a declined or failed identification, for example:

• USER_CANCELLED_PROCESS
• ACCESS_DENIED
• EID_NOT_ACTIVATED
• EID_INVALID

Any other value maps to a generic technical error.

Run the tc-token step manually

Pick an outcome and run it against this environment's callback. An error takes precedence over the card. To complete a real identification, set the session state to one from a live session, otherwise the callback rejects the unknown state.

Card Hans Andre Erika

or error none USER_CANCELLED_PROCESS ACCESS_DENIED EID_NOT_ACTIVATED EID_INVALID

Session state

Callback: https://eid-mock.uat.verimi.cloud/dipp/api/v1/eid/web-flow/callback

Run tc-token

Automation

Automated tests open the authorize URL and the tc-token page auto-completes as the default card with no interaction, so this landing page does not affect them.