Ability to remove or decrease the Passphrase Complexity for RACF

This would give the ability for Single Sign On which could utilize the Active Directory (Windows) as the PRA (Password Rules Authority) and create policies to control password complexity from AD. Currently RACF requires that we utilize a minimum of 2 non-alpha and 2 alpha characters which is controlled at the global level for protection for the passphrase rules. This is currently a non changeable field for RACF.  This prevents AD from using an all alpha or all numeric password due to RACF requirements.  If a company uses 2FA and a long passphrase (15 plus characters)f combined with a product that also validates a password on a block list, the company should be able to modify the complexity rules so AD can become the Rules Authority based on different policies.  

We would like the ability to override those fields using the IRRPHREX and ICHPWX11. We have those 2 exits installed and was unable to override the allowable characters using the Phr_req_types = 2 values hoping that it would only use those categories for the allowable characters, but that is not how it actually works since the 2 non-alpha/2 alpha are internal code.
We would like an enhancement that selecting a lower value for Phr_req_types would require a value from any of those allowable character category. If you changed the value = 1, then you would be allowed a passphrase of 'passwordallowed" or "123456789012345' or a mixed passphrase of 'PAssWord12345@@' using any of the categories with the value of 1 being the only requirement. For more complexity, an option value = 4 would require at least 1 character from each category defined in the IRRPHREX code.

In addition to our change, another request was posted back on March 29, 2022 which stated:

NIST Password Policy Guidelines no longer recommend that password complexity be imposed, since studies have shown they can encourage the creation of bad passwords/passphrases. The manual indicates that RACF enforces a basic set of syntax rules which cannot be altered or avoided, with one of the rules requiring at least 2 non-alphabetic characters. We would like the non-alphabetic character requirement to be optional when creating passphrases.

Also,  researching the Broadcom TSS software, they have currently modified their NEWPHRASE control option to specify the controls for password phrases.