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
Description:
The customer care officer role which is supported in OB2 is "Internal/CustomerCareOfficer". But in OB3, the supported role name is "Internal/CustomerCareOfficerRole". Therefore, we cannot use the migrated customer care officer details to access the consent manager portal in CDS Toolkit.
Also tried to rename the migrated role to the latest one. But it also giving an error "Error: org.wso2.carbon.user.core.UserStoreException: Error updating group information in SCIM Tables."
Suggested Labels:
Suggested Assignees:
Affected Product Version:
OS, DB, other environment details and versions:
Steps to reproduce:
Related Issues:
[Any related issues such as sub tasks, issues reported in other repositories (e.g component repositories), similar problems, etc. ]
The text was updated successfully, but these errors were encountered:
malshaniS
changed the title
[CDSToolkit] - Mismatch in customer care officer role of OB2 and OB3
[CDSToolkit][ConsentMgr] - Mismatch in customer care officer role of OB2 and OB3
Nov 5, 2024
Description:
The customer care officer role which is supported in OB2 is "Internal/CustomerCareOfficer". But in OB3, the supported role name is "Internal/CustomerCareOfficerRole". Therefore, we cannot use the migrated customer care officer details to access the consent manager portal in CDS Toolkit.
Also tried to rename the migrated role to the latest one. But it also giving an error "Error: org.wso2.carbon.user.core.UserStoreException: Error updating group information in SCIM Tables."
Suggested Labels:
Suggested Assignees:
Affected Product Version:
OS, DB, other environment details and versions:
Steps to reproduce:
Related Issues:
[Any related issues such as sub tasks, issues reported in other repositories (e.g component repositories), similar problems, etc. ]
The text was updated successfully, but these errors were encountered: