×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On 13 Mar 2013 12:15, CRPence wrote:
Note: to minimize impact to actual password change requests,
the earliest iterations of the coding might best
set the return indicator to '1' and then immediately return
whenever the user for the job is not the
one that will be used for testing.
Ugh! Correction to the above! The Return Indicator should be set to
'0' and then immediately return whenever the user for the job is not the
user that will be used for testing. Sorry about that... just a bit
difficult for my mind to reconcile immediately that zero=accept and
one=reject, when typically the expectation is that zero=fail and
one=success.
The '0' indicates to accept the password... which means that while
testing, all but the test user would have only the system-rules applied
to their password validation. The password validation program would, by
leaving immediately with Return Indicate = '0', effectively nullify the
invocation of the exit-program for all but the user who was the
designated tester.
This mailing list archive is Copyright 1997-2024 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.
midrange.com
