Why is Oracle implementing a 60 day password change policy for EPM Cloud environments?
This year oracle has implemented a 60 day password expiration strategy. This might be a very good thing for standard user accounts however for service accounts this is an unnecessary hassle. In multi pod environment this becomes a big hassle as now it has to be changed every 60 days in every pod and in encryption files for epm automate servers. Oracle does not have a feature where password change can be scripted. So,enforcing 60 days password policy and not giving an option to change passwords automatically using scripts is creating a big hassle.
I think Oracle needs to have an exception for service accounts or at least give us ability to automate the password change.