Three steps to the first login
- Create an integration. Once the Dorvis team has created your account, set the redirect URI in the self-service portal and get your client_id and client_secret. You can ask for test credentials without a contract.
- Add the OIDC client. Use the Authorization Code flow and the discovery URL from this page.
- Pick a method. With the acr_values parameter you can open a specific method right away, for example idp:smartid.
OpenID Connect
Your server sends the user to Dorvis, receives a code and exchanges it for an ID token. Dorvis communicates with the providers for you.
issuer https://dorvis.eu/oidc
discovery https://dorvis.eu/oidc/.well-known/openid-configuration
flow authorization_code
scope openid profile
acr_values idp:smartid | idp:eparaksts-mobile | idp:eparaksts | idp:eparaksts-scan | idp:eid | idp:swedbank | idp:seb | idp:citadele | idp:luminor | idp:edimDocumentation
The integration is described step by step, from the first login to going live. Every example works with the same Dorvis integration.
Getting started
- QuickstartThe Dorvis team creates the account in the self-service portal after you apply. Once you have it, the first login with Digimaks takes about 15 minutes. Digimaks is on the free plan.
Integration
- Login flowDorvis is an OpenID Connect service using the Authorization Code flow. The user logs in on the Dorvis side, your server receives a code and exchanges it for an ID token.
- EndpointsEvery URL is published in the discovery document. If your library supports it, set only the issuer and let it read the rest.
- Methods and acr_valuesThe
acr_valuesparameter picks which method to open. Without it, the user sees the Dorvis selection page with every method enabled for the integration. - User dataWith
scope=openid profilethe ID token holds a verified first name, last name and personal code, whichever method the user chose. - LogoutTo end the Dorvis session as well, redirect the user to the logout endpoint with the ID token and the URL to return to.
Code
- ExamplesEvery example runs the same flow. It redirects to Dorvis, exchanges the code and reads the personal code. Pick your language.
Operations
- ErrorsErrors are returned in two places: as the
errorparameter on the redirect URI and in the token endpoint response. - SecurityDorvis verifies the identity, and you protect the session and data in your app. These recommendations follow OpenID Connect and OAuth 2.0 good practice.
- Going liveCheck these points before you switch Dorvis login on for real users.
Integrations
What you need to know
- Discovery URL. Every endpoint (authorization, token, jwks, userinfo) is listed in the discovery document, so you do not need to enter them manually.
- acr_values. Without the parameter the user sees every method enabled for your integration. With a value such as idp:smartid they land on that method straight away.
- User data. With the profile scope you receive given_name, family_name and person_code.
- Examples. The guide includes ready-to-run examples you can test locally with your own credentials.
Examples: Node.js, Python, PHP, Java, C#/.NET, Go, WordPress – Examples.
Ready-made integrations
In some cases, you can use an existing integration without developing your own.
- WordPress plugin – Dorvis Auth adds Dorvis to the WordPress login form and links existing accounts.
- Document signing API – Sign documents with eParaksts, eID or Smart-ID straight from your document management system.
Security and compliance
- Keys in a secure vault. Client credentials and provider keys are stored in a separate secure vault.
- Audit log. Every login is recorded so you can show it in an audit.
- Infrastructure in Latvia. Dorvis runs in Latvia, and data processing complies with GDPR.
Did not find the answer?
Write to us and a developer will reply.






