Upper Case Username Cannot View Order Data
(Doc ID 2877502.1)
Last updated on JULY 07, 2022
Applies to:Oracle Communications Order and Service Management - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
Username created in upper case that are members of groups that are a member of OMS_client (ie OSM group association is done on a group rather than on the user) do not work as expected when logging and no roles are associated.
1. create a user TESTUSER1 with uppercase
2. create a user testuser2 with lowercase
Both user associated with user test_group (this group is a member OMS_Client & OMS_xml_api). In the orchestration UI test_group has appropriate roles assigned.
When logging in as testuser2 this works but TESTUSER1 does not work correctly.
Both users we are able to login and search orders in OSM Web Client and Task Client but with TESTUSER1 we are not able to view order data in web client and task data in Task Client. The server logs show the following:
<May 9, 2022 4:34:38,771 PM EEST> <Error> <com.mslv.oms.security.AccessController> <BEA-000000> <Not authorized. The user testuser1 is not authorized to make Access the Order request>
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document