Allow for individual RACF installations to select their own pass phrase controls like Broadcom allows for ACF2

JPMC has a policy regarding pass phrases as follows: 

• Password length of 16 characters or greater must be enforced 
• Passwords must not be one of the last 10 passwords used 
• Passwords must not include the digital identity username 
• Passwords must not contain user’s first or last name 
• Password strength must be verified through an algorithm or pattern validation algorithm to leverage dynamic list of frequently compromised passwords 
• Pattern validation ensures password does not include strings in a firm maintained deny list or include repetitive or sequential patterns more than 3 characters 
• Passwords must be set to expire in 365 calendar days or less 

The policy does not include controls inherent in RACF which are as follows. At least 2 alphabetic characters are specified (A - Z, a - z) At least 2 non-alphabetic characters are specified (numerics, punctuation, special characters, blanks) JPMC needs for the ability in RACF to remove the two controls mentioned above. This is because the JPMC SSO pass phrase will be synced to all platforms and SSO and all other JPMC platforms do not require the character checks. See the policy requirements included above. RACF’s enforcement of at least one non-alpha, non-numeric character in a passphrase breaks JPMC SSO, weakening overall security and portraying the Mainframe as an inflexible platform.  This restriction is not an issue for our ACF2 systems.