Skip to content

Patch hole in scim docs regarding wire team role manipulation. #3897

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

Merged
fisx merged 1 commit into from
Feb 21, 2024
Merged

Patch hole in scim docs regarding wire team role manipulation. #3897

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
1 change: 1 addition & 0 deletions changelog.d/4-docs/wpb-6780-patch-hole-in-scim-docs
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
Patch hole in scim docs regarding wire team role manipulation.
11 changes: 10 additions & 1 deletion docs/src/understand/single-sign-on/trouble-shooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -313,7 +313,16 @@ in your wire team:
mapped on wire's email address, and provisioning works like in
the team management app with invitation emails.

This means that if you use email/password authentication, you **must**
5. SCIM's `roles` is mapped to team role. Only lists of length 0 or 1
are allowed. Valid values are:

- `[member]` (same as `[]`, `null`, or missing field)
- `[admin]`
- `[owner]`
- `[partner]`

The mapping of `externalId` implies that if you use email/password
authentication, you **must**
map an email address to `externalId` on your side. With `userName`
and `displayName`, you are more flexible.

Expand Down