Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions src/pages/docs/platform/account/sso.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -38,6 +38,10 @@ Use the [Okta guide](https://developer.okta.com/docs/guides/saml-application-set
5. Assign users to the newly created Okta application.
6. Note down the **Identity Provider metadata** from Okta.

<Aside data-type='note'>
When a user signs in via SSO for the first time, Ably uses just-in-time (JIT) provisioning to automatically create their account. The `first_name` and `last_name` attributes are used to set the user's display name. If they are missing or empty, provisioning will fail and the user won't be able to sign in. This does not apply if you are using SCIM to provision users.
</Aside>

In your Ably account dashboard:

1. Log in to your [account](https://ably.com/accounts/any).
Expand Down Expand Up @@ -79,6 +83,10 @@ Use the [Google Workspace guide](https://support.google.com/a/answer/6087519?hl=
6. Assign users to the newly created Google Workspace application.
7. Test the SSO connection from Google Workspace.

<Aside data-type='note'>
When a user signs in via SSO for the first time, Ably uses just-in-time (JIT) provisioning to automatically create their account. The `first_name` and `last_name` attributes are used to set the user's display name. If they are missing or empty, provisioning will fail and the user won't be able to sign in. This does not apply if you are using SCIM to provision users.
</Aside>

<Aside data-type='note'>
Google Workspace **alone** does not natively support SCIM.
</Aside>
Expand Down