Skip to content

PORT-11944 Enhance SCIM and AzureAD documentation with improved formatting and updated limitation section #2486

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.

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

Merged
Merged
Show file tree
Hide file tree
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
13 changes: 10 additions & 3 deletions docs/sso-rbac/sso-providers/_scim_functionality_list.mdx
Original file line number Diff line number Diff line change
@@ -1,9 +1,16 @@
### Functionality enabled by SCIM
<h3> Functionality enabled by SCIM </h3>

By enabling SCIM the following functionality will be enabled:

- Automatic deprovisioning of users (for example, when a user is unassigned from the SSO application, that user will automatically lose access to Port).

### Limitations
<h3> Limitations </h3>

- SCIM is currently only supported for customers with a single workspace.
- **Does not support user provisioning** - Only deprovisioning is supported; users must be created manually or through SSO login.
- **Does not sync user attribute updates** - Changes to user profiles in your identity provider will not automatically update in Port.
- **Does not support group provisioning** - Group membership changes in your identity provider are not synchronized via SCIM.
- **Does not provide real-time sync** - SCIM operations may have delays and are not instantaneous.
- **Does not support custom user attributes** - Only standard user fields are processed during deprovisioning.
- **Only supported for customers with a single workspace** - SCIM is not available for multi-workspace setups.

For full user and group synchronization, rely on the SSO login process rather than SCIM.
Loading