ISSUE:
Can you control which users have password controls?
SOLUTION:
Not as delivered. Password controls affect all users.  An enhancement  request has been created for this issue and is tracked by incident 1111500000.  This solution will be updated when this enhancement is completed.
WORKAROUND:
As a workaround all you can do is customize the Password  Controls so they will not affect a user like 'PS'.  Some customers use PS to  start the app server. Starting the app server is a two-tier process so as long  as that is all they are doing they will not be affected by password controls  (password controls like Max logon attempts and expire only work in three tier  and PIA). The problem is that even if this user cannot logon via 3-tier there is  a chance their account could get locked out by possible misuse of someone  attempting to logon as that user id.
To have a user's password never  expire but still be controlled by the max logon attempts you can do the  following:
update PSOPRDEFN set LASTPSWDCHANGE = '2010-12-31' where  OPRID = 'what ever User ID you want'
You would make the LASTPSWDCHANGE  in PSOPRDEFN a future date and then the password would never get this error.  This is good if you create default users to run daily processes.
Remember that any change through the back-end will require you to  recycle the app server cache.
To exclude certain users from the signon  PeopleCode password controls completely here is what you have to do:
1)  In Application Designer open the record called FUNCLIB_PWDCNTL and view the  peoplecode.
2) Open the FieldChange PeopleCode and add the following  right under the line called:
Function PASSWORD_CONTROLS ( );
rem  this is a customization to exclude users from password controls;
If   %SignonUserId = "VP1" Or
           %SignonUserID = "GUEST" Then
  Exit;
End-If;
3) Save & test the new code
Remember  that any changes to delivered code is considered a customization and you will  want to track these changes incase of updates or fixes.
REPORT ID:
1111500000 - Enhancement request has been reported to development
The above solution has been copied from PeopleSoft customer connection. 
Subscribe to:
Post Comments (Atom)
 
 
No comments:
Post a Comment