Single Sign-On (SSO)
Orbit offers Single Sign-On (SSO) capabilities for operator users, enhancing security and streamlining access management.
Orbit offers Single Sign-On (SSO) capabilities for operator users, enhancing security and streamlining access management.
Was this article helpful?
Did not find your answer?
Ask Luna, or write to our support team.
Orbit offers Single Sign-On (SSO) capabilities for operator users, enhancing security and streamlining access management. This feature allows organisations to integrate their existing identity providers with Orbit, providing a seamless authentication experience for their users.
Orbit's SSO implementation supports the SAML 2.0 protocol. When a user attempts to log in:
They are presented with an option for Single Sign-On on the login page
The user enters their email address
Orbit determines the appropriate identity provider based on the email domain
The user is redirected to their organisation's SSO login page
Upon successful authentication, the user is granted access to Orbit
To enable SSO for your organisation, you'll need to provide Orbit with the following information:
Orbit will then provide you with:
When a user logs in via SSO for the first time, Orbit automatically creates a user account based on the information provided by your identity provider. This ensures a smooth onboarding process for new users.
Your identity provider may also manage people who should not work in Orbit MissionControl, such as partners or other companies of your group. In that case, Orbit can admit only users whose identity provider sends a given attribute value, for example only users marked as internal staff. If the attribute holds several values, one allowed value is enough.
A user who is not permitted sees this message on the login page, and no account is created for them:
Your account doesn't have access to Mission. Please contact your administrator.
The restriction is checked when a user signs in for the first time. Once an account exists, a later change of the attribute in your identity provider does not remove it. To take access away from such a user, deactivate them in Orbit MissionControl.
SSO integration enhances security by:
For assistance with SSO configuration or to enable this feature for your organisation, please contact Orbit support. Our team will guide you through the setup process and ensure a smooth integration with your existing identity management system.
Any identity provider that supports SAML 2.0, for example Microsoft Entra ID or PingOne.
The login page shows that their account doesn't have access, and no account is created in Orbit. Once the attribute value is set in your identity provider, the user can sign in again.
No. The restriction is checked on the first sign-in only. To remove an existing user's access, deactivate the user in Orbit MissionControl.