• Subject: Re: Password validation API
  • From: "Ed Fishel" <edfishel@xxxxxxxxxx>
  • Date: Thu, 4 Jan 2001 09:54:47 -0600
  • Importance: Normal


>>Is there a way to validate a password for a user profile other than the
one who is signed on?<<

Take a look at the following three APIs. Get Profile Handle (QSYGETPH) API,
Set Profile (QWTSETP) API, and Release Profile Handle (QSYRLSPH) API which
are documented at


The Get Profile Handle API will take a user-ID and a password, verify the
password and then return a profile handle. The handle can be used to swap
the user profile of the job.

>>The reasoning is that a supervisor could assign a task to a user who does
not have authority to that particular menu option. The supervisor would
then enter his own operator/password combination. When the user leaves the
menu option, the authority is removed.<<

This sounds to me like you are planning to store the supervisors password
and then verify it at a later time. It is never a good idea for a normal
application to store a password. If you need to swap user profile of the
job to the supervisor then it may be better to use a program that uses
adopted authority. A program that adopts the supervisors authority can use
the Get Profile Handle API to get a profile handle for the supervisor
without needing to use the supervisors password. You can then use that
handle to swap the user profile of the job.

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.