• Subject: Re: Password Validation API
  • From: "Ed Fishel" <edfishel@xxxxxxxxxx>
  • Date: Fri, 5 Jan 2001 08:17:44 -0600
  • Importance: Normal

>>A kludge that might work would be ...
>>If the two encrypted passwords match, the password is valid; else, it is
>If you compared the entire return value, this logic would fail since the
>is part of the encryption method for part of the value returned.  It would
>possible to modify your logic to a method which would work, but Leif's
>is a much easier way to accomplish it without incrementing the count for

It may be possible to modify the logic as Doug suggests but it would be
very difficult because the user-id and the password are used as a pair. One
is used to encrypt the other. So since the temporary user profile has a
different object name the encrypted value that is returned will be
different for two user profiles that have the same password.

I think that using the get profile handle is the best choice because it is
easy to use, it increments the incorrect password count for the user
profile, and it audits the fact that an incorrect password was used. It
also has the advantage that it is part of the system and it will be
maintained and supported in future releases. There is no guarantee that the
glob of data returned by the QSYRUPWD (Retrieve Encrypted Password) API, or
the contents of any other internal system control block for that matter,
will be formatted the same in a future release.

Ed Fishel,

| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.