-
Suggestion
-
Resolution: Unresolved
-
None
-
6
-
Problem Definition
It is now possible to sync attributes such as nickname and location via SCIM: https://support.atlassian.com/provisioning-users/docs/sync-user-attributes-to-your-organization
In the case of SCIM, it is possible to configure custom mappings, but in the case of Google Workspace Sync, it is not
Suggested Solution
Provide support for the nickname and location(basedIn) attributes for Google Workspace Sync
Why this is important
Syncing additional attributes will help admins better manage their users
Workaround
No known workarounds aside from using SCIM with Google Cloud - note that Group Memberships don't sync over SCIM with Google Cloud
- was cloned as
-
- Gathering Interest
[ACCESS-2040] Support additional attributes for Google Workspace Sync
| Support reference count | Original: 5 | New: 6 |
| Support reference count | Original: 4 | New: 5 |
| Support reference count | Original: 3 | New: 4 |
| Support reference count | Original: 2 | New: 3 |
| Description |
Original:
h3. Problem Definition
It is now possible to sync attributes such as *nickname* and *location* via SCIM: https://support.atlassian.com/provisioning-users/docs/sync-user-attributes-to-your-organization In the case of SCIM, it is possible to configure custom mappings, but in the case of Google Workspace Sync, it is not h3. Suggested Solution Provide support for the *nickname* and *location*(basedIn) attributes for Google Workspace Sync h3. Why this is important Syncing additional attributes will help admins better manage their users h3. Workaround No known workarounds aside from using SCIM with Google Cloud |
New:
h3. Problem Definition
It is now possible to sync attributes such as *nickname* and *location* via SCIM: https://support.atlassian.com/provisioning-users/docs/sync-user-attributes-to-your-organization In the case of SCIM, it is possible to configure custom mappings, but in the case of [Google Workspace Sync|https://support.atlassian.com/provisioning-users/docs/set-up-g-suite/], it is not h3. Suggested Solution Provide support for the *nickname* and *location*(basedIn) attributes for Google Workspace Sync h3. Why this is important Syncing additional attributes will help admins better manage their users h3. Workaround No known workarounds aside from using SCIM with [Google Cloud|https://support.atlassian.com/provisioning-users/docs/configure-user-provisioning-with-google-cloud/] - note that Group Memberships don't sync over SCIM with Google Cloud |
| Description |
Original:
h3. Problem Definition
It is now possible to sync attributes such as *nickname* and *location* via SCIM: https://support.atlassian.com/provisioning-users/docs/sync-user-attributes-to-your-organization In the case of SCIM, it is possible to configure custom mappings, but in the case of Google sync it is not h3. Suggested Solution Provide support for the *nickname* and *location*(basedIn) attributes for Google sync h3. Why this is important Syncing additional attributes will help admins better manage their users h3. Workaround No known workarounds aside from using SCIM |
New:
h3. Problem Definition
It is now possible to sync attributes such as *nickname* and *location* via SCIM: https://support.atlassian.com/provisioning-users/docs/sync-user-attributes-to-your-organization In the case of SCIM, it is possible to configure custom mappings, but in the case of Google Workspace Sync, it is not h3. Suggested Solution Provide support for the *nickname* and *location*(basedIn) attributes for Google Workspace Sync h3. Why this is important Syncing additional attributes will help admins better manage their users h3. Workaround No known workarounds aside from using SCIM with Google Cloud |
| Summary | Original: Support additional attributes for Google Sync | New: Support additional attributes for Google Workspace Sync |
| Support reference count | Original: 1 | New: 2 |
| Support reference count | New: 1 |
| Component/s | Original: IdP SSO - Google Cloud (G Suite) [ 53304 ] |