SSO Configuration in Semine Admin Pages
You can configure Single Sign-On (SSO) for your organization in Semine. This setup allows users to log in using their existing identity provider, such as Microsoft Entra or Okta.
Follow the steps below to complete the configuration inside Semine’s Admin Pages.
- Select Edit organization in the Admin panel in Semine.
- Open the Single Sign-On Setup tab.
Field Descriptions
- Enabled*: Activate Single Sign-On for the organization. Example: Checked to enable SSO
- Scheme*: Unique identifier automatically generated for the SSO setup. Example: 3f44b0bf-e571-4214-ae70-70d6b4bebda5
- Display Name*: Choose the display name for the login button. Example: Abctest!
- Authority*: Provided by the customer’s IT department or partner. Typically, the login URL from the identity provider.
- Client ID (Application ID)*: Provided by the customer’s IT department or partner.
- Client Secret: Provided by the customer’s IT department or partner.
- Sign-in Scheme*: Authentication scheme used for signing in. Example: idsrv.external
- Sign-out Scheme*: Authentication scheme used for signing out. Example: idsrv
- Callback Path*: Unique redirect path configured in your identity provider’s setup. Example: /signin-3f44b0bf-e571-4214-ae70-70d6b4bebda5
- Validate Issuer: Ensures tokens come from the correct issuer.
- Get claims from userinfo endpoint: Retrieves additional user details like roles or email from the identity provider.
- Clear default scopes: Optional. Clears preconfigured scopes if you want to define custom ones.
- Disable login with SEMINE username and password: Optional. Restricts login to SSO only.
- Scopes: Additional scopes to request from the identity provider. Example: openid profile email
- Domain names*: Customer’s allowed domain(s) for login. Example: domainName1.com, domainName2.com
Note: The values for Authority, Client ID, and Client Secret must be obtained from your identity provider (Microsoft Entra or Okta).
Continue to Provider Setup
After completing the general setup in Semine, continue with the guide for your identity provider:
Comments
0 comments
Please sign in to leave a comment.