What's digiRunner’s well-known URL for OIDC?

[echoari77]

Hi!
I’m setting up OpenID Connect (OIDC) with digiRunner and got a bit stuck on the well-known URL part. Different IdPs seem to format this a bit differently, so I want to make sure my client apps are pointing to the correct discovery endpoint.

What’s the exact format digiRunner uses for
/.well-known/openid-configuration?

Thanks in advance! I’d like to avoid hardcoding the wrong thing 😅

[TPIsoftwareOSPO]

Hi Fiona, thanks for asking 👍

✅ Well-known URL format in digiRunner
In digiRunner, the general format is:

https://{dgr-ip}:{dgr-port}/dgrv4/ssotoken/{idp}/.well-known/openid-configuration

• {dgr-ip} / {dgr-port}: the address where digiRunner is exposed

• {idp}: the IdP name as configured in digiRunner

🔍 Examples
Google as IdP
https://10.20.30.88:18442/dgrv4/ssotoken/google/.well-known/openid-configuration

LDAP / Active Directory
https://{ip}:{port}/dgrv4/ssotoken/LDAP/.well-known/openid-configuration

Custom API-based IdP
https://{ip}:{port}/dgrv4/ssotoken/API/.well-known/openid-configuration

If you’re integrating with Keycloak or another OIDC-compatible provider, just replace {idp} with the name you registered internally in digiRunner.

⚠️ A few gotchas to keep in mind
If you’re using HTTPS on port 443, the port can be omitted from the URL.

Some deployments separate Gateway (GTW) and Admin Console (AC) IdPs, so you may see paths like:

• /gtwidp/

• /acidp/

The {idp} value is case-sensitive and config-driven — always double-check the exact name in your digiRunner configuration.

🧭 In short
Yes — digiRunner follows the OIDC specification and uses the standard
/.well-known/openid-configuration path.
As long as your {idp} matches what’s configured internally, your client applications can safely rely on this discovery endpoint.
Hope this helps! Let us know if you run into any edge cases 👋