Last updated on FEBRUARY 22, 2017
Applies to:Oracle Communications MetaSolv Solution - Version 6.2.1 and later
Information in this document applies to any platform.
MetaSolv Solution Security module behaviors are inconsistent when the system is configured to use Active Directory provider/LDAP authentication instead of the standard Oracle database user account authentication.
1. When creating a new user account using the 'New -> User' function, the system will create a record in SECURITY_USERS, but it does not create an Oracle account for the user ID. This allows for a login to the core MSS client since the user is authenticated against the LDAP source, however this user will not be able to connect to MSS Utilities since an Oracle account is required for authentication. There is no method in Security to create this account other than manually creating the account in the database.
2. When using the 'New From' function, the application will create a user account no matter if the system is using Active Directory provider/LDAP authentication or Oracle database user account authentication.
3. The "Password Expires On" field is hidden from the user maintenance window when the user has logged in via LDAP authentication. A value is still set to the SECURITY_USERS table, but this value is not exposed in the application. Since we need to manage the Oracle account for MSS Utilities purposes, this value needs to be made available.
4. The "Password" and "Confirm Password" fields are both displayed as required (in blue), but the window can be closed and the user successfully created even if they are left blank. If the cursor is placed into one of the fields, it requires a value before the user can leave the field. Since no Oracle user record is being created, whatever information is entered into these fields is lost.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms