After changing encryption mode in solaris (/etc/security/option.conf) from
__unix__ to md5 to avoid minimum lenght password, Iam not able to login to
SBR administrator, even if I revert back to __unix__. Seem /etc/shadow
still point md5 for user root.
Can SBR administrator validate local password with md5 hashing algorithm?
or should I have to revert /etc/shadow to using default algorithm?
I'm not sure md5 passwords are supported for administrator log-in, but I don't see why it wouldn't be. If you are changing from _unix_ to md5, you may need to re-add the administrator so that SBR re-imports the information.
If this is a non-root administrator you just need to remove them from the administrators list in the admin gui, then add them back using the same method.
If this is the root user, you will need to create a file called initial_admin_account.dat which includes the username. Then restart SBR and the file should disappear.
If that doesn't work you should open a case with JTAC so they can dig into it a bit more.
I've follow instruction to create .dat file with username root and restart SBR, but still SBR administrator cannot login with log message 'error authenticating user'.
Then I create another username without md5 encription and its logged successfully. So the conclution is SBR administrator cannot using username with md5 ecrypted password, or there is some knob that I have to change
I would suggest opening a case with JTAC. I don't know of any configuration that will change the password format for administrators.
This is definitely something that we should look into in more detail, so a JTAC case would be best.