About cookies on this site Our websites require some cookies to function properly (required). In addition, other cookies may be used with your consent to analyze site usage, improve the user experience and for advertising. For more information, please review your options. By visiting our website, you agree to our processing of information as described in IBM’sprivacy statement. To provide a smooth navigation, your cookie preferences will be shared across the IBM web domains listed here.
post https://{tenanturl}/v3.0/PasswordPolicies//validate
Entitlement required: anyone (Anyone that has a valid access token).
If the password was found in a bad password dictionary, but the dictionary policy level is set to warning then the header "isv-dictionary-policy" will be returned set to one of "WARNLOCAL" or "WARNGLOBAL"
The password is validated against the password policy and checked whether it is present in the bad password dictionary policy.
Note: Only the passwordStrength elements of the password policy are enforced. However, the passwordStrength passwordMinDiffChars element is not enforced.
If custom password intelligence warning is enabled and a password is provided that is listed in it, the 204 response includes the header 'isv-dictionary-policy' with the value: 'WARNLOCAL'.
If X-Force password intelligence warning is enabled and a password is provided that is listed in it, the 204 response includes the header 'isv-dictionary-policy' with the value: 'WARNGLOBAL'.
If custom password intelligence prevention is enabled and a password is provided that is listed in it, the 400 response can include the header 'isv-dictionary-policy' with the value: 'ENFORCELOCAL'. The corresponding error status is 'PWD_IN_DICTIONARY'.
If X-Force password intelligence prevention is enabled and a password is provided that is listed in it, the 400 response can include the header 'isv-dictionary-policy' with the value: 'ENFORCEGLOBAL'. The corresponding error status is 'PWD_IN_GLOBAL_DICTIONARY'.
Responses
204No Content.