Cleanup Of Userid/Password Settings In Messaging Server, Encountering: Role (suppressed) and Role (emptygroup)
(Doc ID 2317548.1)
Last updated on NOVEMBER 07, 2019
Applies to:Oracle Communications Messaging Server - Version 8.0.1 and later
Information in this document applies to any platform.
Oracle Communications Messaging Server 18.104.22.168.20170906 64bit (built Sep 6 2017)
libimta.so 22.214.171.124.20170906 64bit (built 12:42:11, Sep 6 2017)
Using /opt/sun/comms/messaging64/config/config.xml (compiled)
NSS Library Version: 3.32
We are trying to clean up unnecessary userid/password type settings on all our Messaging Server systems.
We really want userid and passwords set only on systems that actually need them.
And on those systems, have them set to a userid that is specific to that system or role rather than all of them having "admin".
On one of the systems we have cleaned up, msconfig show * output now contains this at the very bottom:
Adding -pass to the show * reveals this:
We had modified our recipe to this, which is causing this output:
The xpass.xml file now contains an empty role called "ims" (without the outside brackets):
[<role name="ims" xmtime="2017-10-11T13:56:29-07:00"/>]
Whereas on other systems where we have not yet done this, that role has sub-elements (excluding the outside brackets):
<proxyadminpass v="..." xuc="IC"/>
<imap_password v="..." xuc="IC"/>
<smtpauthpassword v="..." xuc="IC"/>
It looks like we have deleted the attributes from the "ims" role, leaving an empty role object.
1) Does it matter?
2) Can it be cleaned up?
3) Can we delete those things without creating this situation? Doing a delete -group on "role" seems like a bad idea.
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