Identification with ID Austria
Secure identification in customer service, without security questions.
Your customers confirm their identity with the official Austrian electronic ID, directly from the ongoing contact. Your system receives the result and knows for sure who is asking, at the trust level eIDAS Level High. The solution is based on OpenID Connect and also works with other identity providers.
Who is it really?
Security questions are no longer enough.
Customer service teams usually identify customers with knowledge-based questions such as date of birth, address or customer number. Exactly this data turns up more and more often in data breaches, and phone numbers can be spoofed. With ID Austria, customers confirm their identity with the official electronic ID. Your system then checks whether this identity matches the customer account.
How it works
1. Receive a link
2. Log in with ID Austria
3. Receive the result
Your benefits
Highest trust level
Data minimization under GDPR
Any OIDC provider
Your use cases
Voice agent
Chat
Handover to your team
Use case:
Identification in the voice agent
A caller wants to change their address with their insurance company. This is how the login works during the call. Our demo runs against the ID Austria reference environment with test identities.
1. Recognize the request
2. Code by text message
3. Read out the code
4. Link to ID Austria
5. Log in with ID Austria
6. Back to the conversation
Watch the demo in 4 minutes
A call to an insurance company: the voice agent logs the caller in with ID Austria in the middle of the conversation and receives the result – confirmed, customer number, trust level “high”.
Shown with a public test identity in the ID Austria reference environment. Xenogent Insurance is a fictitious company.
Secure on the phone
Protection against smishing
Protection against spoofed numbers
No hanging up
For IT and architecture:
the technical implementation
OpenID Connect with ID Austria
- Authorization Code Flow with PKCE (S256) and client authentication via
client_secret_post, as required by ID Austria - Endpoints and signature algorithms taken from the identity provider's discovery document, nothing hard-coded
- Full validation of the ID token: signature against the JWKS, issuer, audience, validity, nonce and trust level eIDAS Level High
Stateless auth bridge
The only custom-built component is a lean auth bridge in Node.js and TypeScript. It stores nothing: everything it needs for the return path is encrypted in the OIDC parameter state.
statesealed with AES-256-GCM and limited to 10 minutes; tampered or expired responses are rejected- PKCE verifier and nonce are derived cryptographically from the
state– without a database and without session storage - Matching of first name, last name and date of birth against the candidates from the CRM; the
stateonly contains truncated HMAC values for this, no plain-text data - Result: unique match, no match or ambiguous. The caller is not told the reason for a mismatch.
Feedback into the ongoing call
The bridge reports the result via the Cognigy Inject API directly into the Voice Gateway session. The voice agent only accepts the first valid result for the current request and discards all others.
Running in Azure Austria East
- Azure Container Apps with scale-to-zero; secrets exclusively in Azure Key Vault, accessed via managed identity
- Infrastructure as code with Bicep, deployment via GitHub Actions with OIDC federation instead of stored credentials
- Minimal dependencies, a waiting period for new package versions, signature and vulnerability checks in CI, and a distroless container without root privileges
Experience the live demo
We show you identification with ID Austria using the example of a call, from the call to the approved change of address, and discuss how it can be integrated into your customer service.