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
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.
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.
[1]. https://github.com/wso2-enterprise/identity-migration-resources/blob/master/components/org.wso2.is.migration/migration-resources/5.10.0/stored-procedures/user_id_migration/oracle.sql#L57
Thanks,
Viraj.
The text was updated successfully, but these errors were encountered: