Use OpenID Connect in Slite to allow users to securely sign in with Azure Active Directory identities. It will also become the people can sign into Slite.
.1In your Active Directory, click "Add" and choose "App registration":
.2Choose a name for this app, for example Slite
.
.3In "Select a Platform", select "Web".
.4In the Redirect URI enter: https://slite.com/api/auth/openid/callback
.5Click "Register".
You should now find your App under Applications > App registrations:
Click on your app registration to see your
.1In your new app registration, click "Certificates & secrets".
.2Click "New client secret".
.3In "Description", enter something you'll remember, e.g. the name of your Slite workspace.
.4In "Expires", the default is "180 days". This is shorter than most SSO providers, and we recommend a higher value. After this expiry, you'll be locked out of your Slite account until you manually update your client secret.
.5Copy the "Value" of your new client secret. (Not its Secret ID.)
.1Click your team avatar in the left sidebar, and click "Team settings".
.2Click the "Security" tab in the left sidebar.
.3Next to "SSO authentication enforcement", click "Expand".
.4Next to "OpenID authentication", click "Configure". You should now see this form:
.5In "Provider name", enter the name you wish to display on your Slite login page. (This is not used as part of the technical auth process.)
.6In "Provider URL", enter https://login.microsoftonline.com/TENANT-ID/v2.0
, replacing TENANT-ID
with the Tenant ID that you noted down earlier.
.7Under "Client ID", enter the Client ID that you noted down earlier.
.8Under "Client secret", enter the Client secret that you noted down earlier.
.9Click "Validate and save". It should redirect you to Azure Active Directory's authentication portal.
.10Identify yourself, click "Consent on behalf of your organisation", and click Accept. You should be redirected to Slite.
.11The SSO configuration process is over. Validate that your SSO login works.