Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Training Question of the Week for January 14, 2008

Updated on November 15, 2015

Question
Does PRPC provide a way to enforce password compliance requirements without additional software? I would like a developer's password to expire every 90 days, prevent repeated passwords, and be able to enforce what characters are allowed in a password.

Answer from Jeff Vande Wege
Version 5.3 introduced an optional Password Control feature, implemented as a RuleSet. You import a Password Control RuleSet from the 5.3 Resource Kit directory of the distribution kit (which includes documentation) and then configure password requirements.

Requirements include defining naming restrictions, length, expiration date, preventing reuse and first login reset. You can also build in your own custom requirements.

For more information on Password Control see the Password Control help topic.



Answered by Jeff Vande Wege

See Index: Training Questions of the Week for more questions and answers.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Visit the Support Center

Did you find this content helpful?

Yes
No

Want to help us improve this content?
Suggest an edit

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us