| Asset ID: |
1-71-2359372.1 |
| Update Date: | 2018-02-14 |
| Keywords: | |
Solution Type
Technical Instruction Sure
Solution
2359372.1
:
Request Detailed Info On Password Aging In Diameter Signaling Router (DSR) Mixed Software Environment
| Related Items |
- Oracle Communications Diameter Signaling Router (DSR)
|
| Related Categories |
- PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec DSR
|
In this Document
Created from <SR 3-16410525091>
Applies to:
Oracle Communications Diameter Signaling Router (DSR) - Version DSR 7.3.0 and later
Information in this document applies to any platform.
Goal
Requesting detailed info on Password Aging in a mixed software environment.
The NOAM has been upgraded to 7.3.1, but the SOAMs are still on 5.1.0-51.20.1.
We have been advised to run the Inhibit Password Aging workaround procedure in all remaining sites that are on the 5.1.0 software.
Reference to the Appendix M-1 of Oracle 7.3.1 software upgrade Procedure
We have some specific questions regarding the script, and how it functions.
The text file to be added in each SOAM running 5.1.0 sw is as follows:
[production]
aw.policy.pwchange.isExpired =
aw.policy.db.checkPw =
aw.policy.login.checkPw =
[development : production]
[test : development]
Specific Questions:
- Lines 1, 4 and 5 have brackets. What are these lines for, are they needed?
- Lines 2 and 3 have no value after the = , is this still correct?
- How is password aging currently being done now, is there a difference between 5.1.0 and 7.3.1 software environments?
- Where is password aging being enforced, NOAM or SOAMs?
- Is there another way to get around individual users that have passwords expired?
- Are there any applications or processes that read or reference this new workaround script that might be impacted?
- What does the "clearCache" command actually do?
Solution
- Lines 1, 4 and 5 have brackets. What are these lines for, are they needed?
Yes they are needed for the appwworks (the application that controls GUI)
- Lines 2 and 3 have no value after the = , is this still correct?
yes that is correct
- How is password aging currently being done now, is there a difference between 5.1.0 and 7.3.1 software environments?
Password configuration, such as setting passwords, password history rules, and password expiration, occurs in NOAM GUI >> Administration >> General Options
The application provides a way to set passwords: through the user interface from the Administration >> Access Control >> Users
For more detailed please refer to the Administration chapter in [1] Operation, Administration, and Maintenance (OAM) Guide.
- Where is password aging being enforced, NOAM or SOAMs?
password aging is enforced at NOAM
- Is there another way to get around individual users that have passwords expired?
No. The only available options are:
1. Perform this mentioned workaround (Appendix M of Upgrade Procedure for DSR 7.3)
2. Upgrade the SOAMs
- Are there any applications or processes that read or reference this new workaround script that might be impacted?
No
- What does the "clearCache" command actually do?
It refreshes all the cache files for the SOAM on which it is run.
- Should the procedure be applied on spare SOAM too?
Yes.
IMPORTANT NOTE
The script for password aging (one example shown above) changes between different releases. So make sure that the upgrade guide being referred applies to the mixed mode releases of customer.
For example, if the lower release is 5.1.0 and higher release is 7.3.1, then the standard procedure mentioned in upgrade documentation of 7.3.x will not be not applicable because 5.1 to 7.3.x is not a supported upgrade path.
The example script shown above is only if one release is 5.1.0 and the other release is 7.3.1 in a mixed mode release.
Attachments
This solution has no attachment
