SCIM claim mapping issue for migrated secondary user store users
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 99
- Forks
- 708
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 22
Description
Hi Team,
The customer is migrating API Manager 2.6.0 and Identity Server 5.7.0 as Key Manager to API Manager 4.2.0 and Identity Server 6.1.0 as Key Manager. They have already completed the migration. On the Identity Server side, they are using JDBC secondary user stores.
In the migrated environment, they are facing an issue with claim mapping while authenticating secondary userstore users with a federated IDP. They have further tested and identified that manually mapping the scimId to the particular user’s attribute in the database resolves the issue.
Since there is stored procedure[1] available to add the scimid to the user attribute table for all migrated user. This [1] stored procedure need to add to the migration documentations.
Thanks,
Viraj.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked migration resource at components/org.wso2.is.migration/migration-resources/5.10.0/stored-procedures/user_id_migration/oracle.sql, especially line 57, and locate the corresponding API Manager migration documentation. Document the stored procedure for adding scimId values to migrated secondary user-store users, then verify that the procedure and its purpose are clearly covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql
- Domain
- databases, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100