Single sign-on (SSO)
Platform.sh allows you to set up mandatory SSO with a third-party identity provider (IdP) for all your users.
Your SSO provider can be enabled for a specific email domain, for example
@example.com. Every user with a matching email address will have to log in or register on Platform.sh using your SSO provider. Such users will not be able to use an alternative provider, or register a password, or change their email address.
If you deactivate a user on your identity provider, they will not be able to log in or register on Platform.sh.
If the user is already logged in to Platform.sh, they will be automatically deactivated after their access token has expired (generally after 1 hour).
A deactivated user will no longer be able to use SSH, Git, or other Platform.sh APIs.
If you have a service user with an email address under your SSO domain, e.g.
firstname.lastname@example.org, you can exclude that user from the SSO enforcement rule so that they will not be required to authenticate through your identity provider.
Please open a support ticket if you need to exclude a service user.
Enforce your users to authenticate with Google. Please open a support ticket to enable Google SSO.
If your organization has Google SSO enabled on Platform.sh, you may be required to re-authenticate with Google every 15 minutes. This happens when Platform.sh does not possess a valid refresh token from your Google account.
To resolve that, you need to:
- Go to https://myaccount.google.com/permissions and revoke the access from the
Platform.shapplication that has
Access given to auth.api.platform.sh.
- Go to https://auth.api.platform.sh/auth/authorize/google?consent=prompt for the system to obtain a valid refresh token for your Google account.
Enforce your users to authenticate with your OpenID Connect provider. Please open a support ticket to enable SSO with your OpenID Connect provider.