The Login Exclusion Configuration Was Not Effective
Last updated on JULY 27, 2017
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
On : 18.104.22.168.0 version, Activity Opcodes
In order to improve performance of real-time AAA requests by searching for the service using aliases rather than the login, a custom services for login exclusion has been configured as described in the BRM documentation:
However, when performing a real-time AAA request, CM logs showed that BRM was still searching for the service using the login first and then using the aliases.
The /config/login_exclusion object in the BRM data was verified as correct and CM has been restarted, but it seemed that the login exclusion configuration was not effective.
AAA requests by searching for the service still using the login first.
AAA requests by searching for the service should be using the aliases first.
The issue can be reproduced at will with the following steps:
1. Configure /config/login_exclusion to search alias names first and login names second for specified service types
2. Restart the system
3. Perform AAA opcodes
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms