Skip to content
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

SCIM2 Outbound Provisioning Fails for Custom Attributes #22191

Open
Manchiz opened this issue Jan 7, 2025 · 0 comments
Open

SCIM2 Outbound Provisioning Fails for Custom Attributes #22191

Manchiz opened this issue Jan 7, 2025 · 0 comments

Comments

@Manchiz
Copy link

Manchiz commented Jan 7, 2025

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

  1. Create a custom claim attribute [1] and enable the Display this attribute required in user’s profile option.
  2. Configure SCIM2 outbound provisioning [3].
  3. Create a user and check whether the custom claim is provisioned.

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/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

2 participants