You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It was observed that SCIM2 outbound provisioning does not handle custom attributes properly. When a custom attribute is created, it is categorized under SCIM2 custom schema attributes [1]. However, during SCIM2 outbound provisioning, the claim dialects are hardcoded, and the SCIM2 custom dialect is missing [2].
As a result, custom claims are not provisioned. Even if custom claims are added to the Provisioning Attributes Selection in the provisioning connector, they still fail to be provisioned.
Steps to Reproduce
Create a custom claim attribute [1] and enable the Display this attribute required in user’s profile option.
Configure SCIM2 outbound provisioning [3].
Create a user and check whether the custom claim is provisioned.
Description
It was observed that SCIM2 outbound provisioning does not handle custom attributes properly. When a custom attribute is created, it is categorized under SCIM2 custom schema attributes [1]. However, during SCIM2 outbound provisioning, the claim dialects are hardcoded, and the SCIM2 custom dialect is missing [2].
As a result, custom claims are not provisioned. Even if custom claims are added to the
Provisioning Attributes Selection
in the provisioning connector, they still fail to be provisioned.Steps to Reproduce
Display this attribute required in user’s profile
option.Version
7.0.0
[1]. https://is.docs.wso2.com/en/latest/guides/users/attributes/manage-attributes/#add-custom-attributes
[2]. https://github.com/wso2-extensions/identity-outbound-provisioning-scim2/blob/acef313c5d30c2c7c4550d8540ca9536c3fa762f/components/org.wso2.carbon.identity.provisioning.connector.scim2/src/main/java/org/wso2/carbon/identity/provisioning/connector/scim2/SCIM2ProvisioningConnector.java#L362
[3]. https://is.docs.wso2.com/en/latest/guides/users/outbound-provisioning/provisioning-levels/org-level/
The text was updated successfully, but these errors were encountered: