Configuring SSO with Conduktor Desktop
Connection Name
that we’ll share. It’s most likely going to be your company name converted in kebab-case (a-z
, 0-9,
or -
). In the following examples, we’ll use your-company
.
You first need to declare a new SAML 2.0 Application in your IdP.
There are two important fields you need to declare your Application:
Item | Example |
---|---|
Post-back URL or ACS URL | https://auth.conduktor.io/login/callback?connection=`your-company` |
Entity ID | urn:auth0:conduktor:your-company |
email_verified
with the value true
. email
must be present and lowercaseItem | Example |
---|---|
SSO URL | https://login.your-company.com/sso/saml |
Signing Certificate | A .cer, .crt or .pem file |
Domain names to redirect authentication | your-company.com , subsidiary-company.com |
Server-side
or Web Application
type.
Leave most default as-is except for the “Sign-in redirect URL”: https://auth.conduktor.io/login/callback
email_verified
with the value true
. email
must be present and lowercaseItem | Example |
---|---|
Client ID | 0oaztxq9vavFnY9wh696 |
Client Secret | zTRaILrMOgFGHjHm5J_nrUuv3WPXTYoaj9r3jytl |
Provider Configuration URI | https://login.your-company.com/.well-known/openid-configuration |
Domain names to redirect authentication | your-company.com , subsidiary-company.com |