PeopleTools and Lifecycle Management - PSFT (MOSC)

MOSC Banner

Changing hashed password value

edited Aug 21, 2012 4:32AM in PeopleTools and Lifecycle Management - PSFT (MOSC) 3 commentsAnswered
Our users authenticate to PeopleSoft through active directory.  Therefore, they generally do not use their PeopleSoft passwords.  The hashed value of the operator password is stored in the operpswd field of the psoprdefn table.  In order to ensure that nobody has a PeopleSoft password that is not secure enough, I am considering doing a mass update of the operpswd field to a random hashed value.  This would prevent anyone from having a usable PeopleSoft password.  Can anyone think of any problems with this approach?

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

PSFT PeopleTools Tags

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center