Skip to content

Docs: Add JIT provisioning context to SSO first_name/last_name requirement #3336

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ably-sync-bot wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Docs: Add JIT provisioning context to SSO first_name/last_name requirement #3336

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7052779
Update callout to explicitly reference first_name and last_name attri…
ably-sync-bot Apr 14, 2026
27c3cac
Eliminate duplicate SSO provisioning note
mclark-ably Apr 20, 2026
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
View file
Open in desktop
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'>
Copy link
Copy Markdown
Contributor

@m-hulbert m-hulbert Apr 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd suggest moving this up to L18 (at the end of 'Configure' to save having to repeat it for both Okta and Google.

Copy link
Copy Markdown
Contributor

@mclark-ably mclark-ably Apr 20, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed, I have removed the duplication and moved it to L18. Does that look ok now?

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