-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
Severity 3 - Minor
-
Disclaimer
This difficulty was already described in another Bug report (ACCESS-766) therefore, to avoid confusion, this one will be closed. Please keep tracking this issue on ACCESS-766.
Apologies for the inconvenience.
Issue Summary
The Based in field is gets locked out on Managed accounts of a Organization when the SCIM integration is enabled.
However, the SCIM does not support that field yet (there is no matching Target attribute) therefore, the admins can edit that through the IdP sync neither at the Org side.
Steps to Reproduce
- Integrate with SCIM
- Try to update that field at Org > Directory > Managed accounts > User profile or at the IdP.
Expected Results
The field would get updated through the SCIM integration.
Actual Results
- The SCIM does not support the field.
- The admins can't change that manually due to the integration.
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available
- duplicates
-
ACCESS-766 Based in (location) cannot be updated via user provisioning
-
- Closed
-
[ACCESS-771] Unable to edit "Based in" field when SCIM is enabled
Link |
New:
This issue duplicates |
Resolution | New: Duplicate [ 3 ] | |
Status | Original: Needs Triage [ 10030 ] | New: Closed [ 6 ] |
Description |
Original:
h3. Issue Summary
The *Based in* field is gets locked out on Managed accounts of a [Organization|https://confluence.atlassian.com/cloud/organization-administration-938859734.html] when the SCIM integration is enabled. !image.png|thumbnail! However, the SCIM does not support that field yet (there is no matching *Target attribute*) therefore, the admins can edit that through the IdP sync neither at the Org side. h3. Steps to Reproduce # Integrate with SCIM # Try to update that field at Org > Directory > Managed accounts > User profile or at the IdP. h3. Expected Results The field would get updated through the SCIM integration. h3. Actual Results # The SCIM does not support the field. # The admins can't change that manually due to the integration. h3. Workaround Currently, there is no known workaround for this behavior. A workaround will be added here when available |
New:
h3. Disclaimer
{panel:borderStyle=solid|borderColor=#6A8EB3 |bgColor=#F8F8F8} (!) This difficulty was already described in another Bug report ([ Apologies for the inconvenience. {panel} h3. Issue Summary The *Based in* field is gets locked out on Managed accounts of a [Organization|https://confluence.atlassian.com/cloud/organization-administration-938859734.html] when the SCIM integration is enabled. !image.png|thumbnail! However, the SCIM does not support that field yet (there is no matching *Target attribute*) therefore, the admins can edit that through the IdP sync neither at the Org side. h3. Steps to Reproduce # Integrate with SCIM # Try to update that field at Org > Directory > Managed accounts > User profile or at the IdP. h3. Expected Results The field would get updated through the SCIM integration. h3. Actual Results # The SCIM does not support the field. # The admins can't change that manually due to the integration. h3. Workaround Currently, there is no known workaround for this behavior. A workaround will be added here when available |
Description |
Original:
h3. Issue Summary
The *Based in* field is gets locked out on Managed accounts of a [Organization|https://confluence.atlassian.com/cloud/organization-administration-938859734.html] when the SCIM integration is enabled. !image.png|thumbnail! However, the SCIM does not support that field yet (there is no matching *Target attribute*) therefore, the admins can edit that through the IdP sync neither at the Org side. h3. Steps to Reproduce # Integrate with SCIM # Try to update that field at Org > Directory > Managed accounts > User profile or through the IdP. h3. Expected Results The field would get updated through the SCIM integration. h3. Actual Results # The SCIM does not support the field. # The admins can't change that manually due to the integration. h3. Workaround Currently, there is no known workaround for this behavior. A workaround will be added here when available |
New:
h3. Issue Summary
The *Based in* field is gets locked out on Managed accounts of a [Organization|https://confluence.atlassian.com/cloud/organization-administration-938859734.html] when the SCIM integration is enabled. !image.png|thumbnail! However, the SCIM does not support that field yet (there is no matching *Target attribute*) therefore, the admins can edit that through the IdP sync neither at the Org side. h3. Steps to Reproduce # Integrate with SCIM # Try to update that field at Org > Directory > Managed accounts > User profile or at the IdP. h3. Expected Results The field would get updated through the SCIM integration. h3. Actual Results # The SCIM does not support the field. # The admins can't change that manually due to the integration. h3. Workaround Currently, there is no known workaround for this behavior. A workaround will be added here when available |