Re: Password Validation API

The API you're using requires a user id because:
"The user profile name is used when checking the password rules for system
values Required Difference in Passwords (QPWDRQDDIF) and Password Rule -
password may not contain user name (QPWDRULES *LMTPRFNAME)."
Try the API the other person suggested instead.
Or the work around of using a dummy user id suggested by another person
#IBMChampion

On Thu, Feb 2, 2023 at 3:59 PM Steve McKay <samckay1@xxxxxxxxx> wrote:

All -

Is there an API (or other method) that will validate a password against the
QPWD* system values without an associated user name? I just want to feed
the password to the API or program and get back a 'YES'/'NO' indicating it
passed/failed the QPWD* system value composition rules.

We are trying to build a process that will accept user profile
add/change/delete requests from a non-IBM i product. We would like to
allow the admins of the product to enter a non-user user profile and the
desired password into the product. Then we would run a scrub program on
the data coming into the IBM i to check the password against IBM i QPWD*
system values to be sure that it will pass when we use it in the CRTUSRPRF
command.

I have looked at the QSYCHGPW API but it wants an existing user profile and
password. I have also looked at the Validate Password Exit Point/Program
but we don't want to do this for all user password changes, only the new
non-user profile/password requests from the 3rd party product.

We understand that there are probably better ways to do this but, for a
narrow scope of non-user profiles, we would like to provide this
functionality without writing our own program.

Any suggestions?

Thanks,

Steve McKay
(205) 585-8424
samckay1@xxxxxxxxx
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.