SSO is fully self-service for the two most common identity providers — you configure both sides yourself, no need to contact us:
- Microsoft Entra ID (Azure AD) — in the Azure Enterprise applications dashboard, create a non-gallery SAML application pointed at our Assertion Consumer Service URL (
https://inventory.stage.sdsmanager.com/saml2_auth/acs/), then in SDS Manager go to Settings → Single Sign-On and enter that app's Federation Metadata URL and Application ID yourself, then click Save. Custom app roles (Admin, Staff, Read Only, Admin Light) map directly to SDS Manager roles. - Okta — create a SAML 2.0 app integration with the Single Sign-On URL set to
https://inventory.stage.sdsmanager.com/saml2_auth/acs/and Default RelayState set tohttp://inventory.stage.sdsmanager.com/sso-login/, then in SDS Manager go to Settings → Single Sign-On and enter the Okta App ID yourself, then click Save. Group attribute statements let Okta groups map straight to SDS Manager roles.
Both are IT-admin-level setups with several steps on the identity-provider side, so we won't try to cram the full walkthrough into an FAQ answer — but once you have those values, the SDS Manager side is just this one self-service form: paste in the metadata URL/App ID, click Save, and use the Test button on that same Settings page to confirm the connection before rolling it out to your team.
SSO/ADFS integration is listed as an Enterprise-only capability on SDS Manager's own published plan-comparison table (not included even on Pro) — check with your account team if you're not sure which plan you're on.

Comments
0 comments
Nothing here yet. Comments will appear here.
Sign in to leave a comment