Re: Expired password change anomaly -- MIDRANGE-L

Subject: Re: Expired password change anomaly
From: "James H. H. Lampert" <jamesl@xxxxxxxxxxxxxxxxx>
Date: Tue, 08 Jul 2014 16:06:40 -0700
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Monnier, Gary wrote:

Seems to me if you are obtaining a handle for a profile with an
expired password and are not using *NOPWDCHK or *NOPWDSTS for the
password parameter you may have found a serious bug.

Seems to me that we're using the call to QSYGETPH only to determine whether the password is (1) correct, and (2) expired. Since we spawn off jobs, rather than doing profile-swaps, we don't actually use the profile handle; we only care about the exception (or lack thereof).

Therefore, using *NOPWDCHK or *NOPWDSTS would defeat our whole purpose of calling QSYGETPH. Besides, if we KNEW whether the password was correct, and whether or not it was expired, we wouldn't have any reason to call QSYGETPH in the first place.

--
JHHL

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: Expired password change anomaly , Monnier, Gary

This mailing list archive is Copyright 1997-2025 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.