What you need before you start
- A Microsoft Entra External ID external tenant and a user with at least the External Identity Provider Administrator role. OpenID Connect identity provider support has been generally available since 18 March 2025.
- A Dorvis integration in the self-service portal. Smart-ID, eParaksts and bank login need a paid plan.
- Access to Microsoft Graph (for example Graph Explorer) to make the e-mail attribute optional, because Dorvis does not return an e-mail.
Add Dorvis as a custom OpenID Connect provider
Register the Entra redirect URIs in Dorvis
In the Dorvis portal add both
https://TENANT-SUBDOMAIN.ciamlogin.com/TENANT-ID/federation/oauth2andhttps://TENANT-SUBDOMAIN.ciamlogin.com/TENANT-SUBDOMAIN.onmicrosoft.com/federation/oauth2. Copy the client ID and client secret.Open the custom providers
In the Microsoft Entra admin center go to Entra ID → External Identities → All identity providers, open the Custom tab and choose Add new → Open ID Connect.
Fill in the basics
Set Display name (users see it on the sign-in button), Well-known endpoint
https://dorvis.eu/oidc/.well-known/openid-configuration, OpenID Issuer URIhttps://dorvis.eu/oidc, the Dorvis Client ID and Client Secret.Choose authentication, scope and response type
Set Client Authentication to
client_secret_post(Entra does not supportclient_secret_basic, andprivate_key_jwtis not supported yet). Set Scope toopenid profile. Response type must becode.Map the claims
Select Next: Claims mapping and map the values as in the table below. Leave Email unmapped; then select Review + create.
Add it to a user flow
Open your sign-up and sign-in user flow, add the Dorvis provider under its identity providers and save. Then make the e-mail attribute optional, as described below.
Claims mapping for Dorvis
| Entra field | Dorvis claim | Note |
|---|---|---|
| Sub | sub | Stable identifier of the person in your integration |
| Name | name | Shown in the account picker |
| Given name | given_name | Verified by the e-identity provider |
| Family name | family_name | Verified by the e-identity provider |
| leave empty | Dorvis sends no e-mail; make the attribute optional in the user flow | |
| Personal code | not available | The External ID mapping has no field for custom claims such as person_code |
Make e-mail optional in the user flow
Without this, sign-up through Dorvis fails with AADSTS901011: No email address was obtained from the external oidc identity provider. Send the complete list of attribute inputs, not just e-mail, and note that the change applies to every application using the user flow.
PATCH https://graph.microsoft.com/v1.0/identity/authenticationEventsFlows/{user-flow-id}
Content-Type: application/json
{
"@odata.type": "#microsoft.graph.externalUsersSelfServiceSignUpEventsFlow",
"onAttributeCollection": {
"@odata.type": "#microsoft.graph.onAttributeCollectionExternalUsersSelfServiceSignUp",
"attributeCollectionPage": {
"views": [{
"inputs": [
{ "attribute": "email", "label": "Email Address", "inputType": "text", "required": false, "...": "..." },
{ "...": "all other existing inputs of the flow, unchanged" }
]
}]
}
}
}Limits of the custom OIDC provider
No method selection. Entra builds the authorization request from the Dorvis metadata and documents no way to add acr_values, so users see the Dorvis chooser with every method enabled in your integration. To offer only Smart-ID, enable only Smart-ID in that Dorvis integration.
No personal code in Entra. The claims mapping covers standard claims only. If an application needs person_code, let it run its own OpenID Connect login against Dorvis for that step, or use Azure AD B2C custom policies if you are an existing B2C customer.
Issuer changes. If you change the Issuer URI later, Microsoft notes it may not take effect in user flows until you disable the provider in the flow, save, enable it again and save.
Alternative for existing Azure AD B2C tenants: custom policy
Azure AD B2C has not been sold to new customers since 1 May 2025; Microsoft supports existing tenants until at least May 2030. In a B2C custom policy an OpenID Connect technical profile can send acr_values as an input claim and read person_code as an output claim. Declare acr_values and personCode in your ClaimsSchema and register https://TENANT.b2clogin.com/TENANT.onmicrosoft.com/oauth2/authresp in Dorvis.
<TechnicalProfile Id="Dorvis-SmartId">
<DisplayName>Smart-ID</DisplayName>
<Protocol Name="OpenIdConnect" />
<Metadata>
<Item Key="METADATA">https://dorvis.eu/oidc/.well-known/openid-configuration</Item>
<Item Key="client_id">DORVIS_CLIENT_ID</Item>
<Item Key="response_types">code</Item>
<Item Key="scope">openid profile</Item>
<Item Key="HttpBinding">POST</Item>
<Item Key="UsePolicyInRedirectUri">false</Item>
</Metadata>
<CryptographicKeys>
<Key Id="client_secret" StorageReferenceId="B2C_1A_DorvisClientSecret" />
</CryptographicKeys>
<InputClaims>
<InputClaim ClaimTypeReferenceId="acr_values" DefaultValue="Smartid" />
</InputClaims>
<OutputClaims>
<OutputClaim ClaimTypeReferenceId="issuerUserId" PartnerClaimType="sub" />
<OutputClaim ClaimTypeReferenceId="givenName" PartnerClaimType="given_name" />
<OutputClaim ClaimTypeReferenceId="surname" PartnerClaimType="family_name" />
<OutputClaim ClaimTypeReferenceId="personCode" PartnerClaimType="person_code" />
<OutputClaim ClaimTypeReferenceId="identityProvider" DefaultValue="dorvis.eu" />
<OutputClaim ClaimTypeReferenceId="authenticationSource" DefaultValue="socialIdpAuthentication" />
</OutputClaims>
<UseTechnicalProfileForSessionManagement ReferenceId="SM-SocialLogin" />
</TechnicalProfile>Did not find the answer?
Write to us and a developer will reply.






