Harvest Password Policy Standards

Products

• CA Harvest Software Change Manager
• CA Harvest Software Change Manager
• CA Harvest Software Change Manager - OpenMake Meister

Issue/Introduction

Does the application force users to change their passwords as required by our company's policy-based intervals?  Does the application enforce password complexity that matches our company's standards?  (for example, at least 2 upper, 2 lower, 2 numeric, & 2 special characters)  Could you give me some examples of changing password from 90 to 60 days.

Environment

Harvest Software Change Manager all versions

 

Cause

The way the password policy works in Harvest is

1. You use the hppolget command to export the password policy settings to a text file.  
2. Then you use Notepad (or vi on a Linux server) to update the text file and change the settings you want to change.  
3. Finally you use the hppolset command to import the file again to the Harvest database.

Resolution

For example, to change the maximum password age to 60 days,

1. Execute:

   hppolget -b <brokername> -prompt -f policy.txt

2. Execute:

   notepad policy.txt (or "vi policy.txt" if you're doing this on Linux)

3. Change the desired settings in the policy.txt file, for example:
   1. To change the maximum password age, set maximumpasswordage to your desired value.
   2. To change the required password makeup, set minimumnumericcharacter, minimumlowercasecharacter, minimumuppercasecharacter, minimumnonalphanumericcharacter, maximumrepeatablecharacter, minimumpasswordlength to your desired settings
   3. To force password change at next login, set forcechange to "true"
4. Execute:
   hppolset -b <brokername -prompt -f policy.txt

Additional Information

Information about the hppolget command is here: hppolget Command-Get Password Policy

Information about the hppolset command (including all the settings that are available to change) is here: hppolset Command-Set Password Policy