Re: 7.3: CHGUSRPRF PASSWORD(...)

😂😂😂👍

Jay

On Jan 28, 2019, at 8:45 AM, Rob Berendt <rob@xxxxxxxxx> wrote:

I disagree, and I could put a comment in here about changing all job ended abnormally to ended normally, since, after all, they did end, but it's a waste of effort on everyone's part and a thread which should just die.



-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Kevin Bucknum
Sent: Monday, January 28, 2019 8:09 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: 7.3: CHGUSRPRF PASSWORD(...)

That was what I was trying to point out.
Issue CHGUSRPRF ROB with no other parameters.
You will get the success message even though you didn't give it anything to actually change. It does update the last changed date on the user profile itself, so that must be what it is reporting as changed.



-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of Rob Berendt
Sent: Sunday, January 27, 2019 2:38 PM
To: Midrange Systems Technical Discussion
Subject: RE: 7.3: CHGUSRPRF PASSWORD(...)

So when it said it was changed successfully, what was changed?

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Evan Harris
Sent: Friday, January 25, 2019 6:13 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: 7.3: CHGUSRPRF PASSWORD(...)

Well what you've found seems reasonable to me. CHGUSRPRF is for changing the profile object not just the password exclusively.

On Sat, 26 Jan 2019, 08:08 Rob Berendt <rob@xxxxxxxxx wrote:

One can run
CHGUSRPRF USRPRF(...) PASSWORD(different) CHGUSRPRF USRPRF(...)
PASSWORD(original) And the date password last changed will change.
And a new date that the password will expire will display.
My problem was that when I thought I was running CHGUSRPRF USRPRF(...)
PASSWORD(different) It wasn't a different password. Therefore, even
while CHGUSRPRF reported that it ran successfully the password was
unchanged and still listed as expired.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Musselman, Paul
Sent: Friday, January 25, 2019 1:47 PM
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: 7.3: CHGUSRPRF PASSWORD(...)

Wouldn't the unchanged 'last changed' date still trip the 'password
expired,' based on the password expiration interval?

I'm pretty sure that once the 'password expired' (or nearly expired)
flag is set, you MUST change your password, and even CHGUSRPRF won't fix it.
):

Paul E Musselman
PaulMmn@xxxxxxxxxxxxx
.
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Rob Berendt
Sent: Friday, January 25, 2019 10:59 AM
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: 7.3: CHGUSRPRF PASSWORD(...)

DSPUSRPRF ROB
Date password last changed . . . . . . . . : 11/13/18 11:25:28

CHGUSRPRF USRPRF(ROB) PASSWORD()
User profile ROB changed.
I used my current password

DSPUSRPRF ROB
Date password last changed . . . . . . . . : 11/13/18 11:25:28
Time sent . . . . . . : 10:46:14

DSPJRN JRN(QAUDJRN) RCVRNG(*CURCHAIN)
FROMTIME(012519 104600) TOTIME(012519 104700) No CP entry.

I guess that answers my question right there. CHGUSRPRF checks the
before/after and doesn't update the password last changed date if you
don't really change the password

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Charles Wilt
Sent: Friday, January 25, 2019 10:40 AM
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: 7.3: CHGUSRPRF PASSWORD(...)

My understanding is that CHGUSRPRF doesn't go through any of the
password checks..

CHGPWD is what the application should be using

Charles

On Fri, Jan 25, 2019 at 8:35 AM Rob Berendt <rob@xxxxxxxxx> wrote:

Let's say you have a user. You know the password. You know it's

expired.

If you do a CHGUSRPRF USER(...) PASSWORD(...same password...) Will
you get the CPC2205 - User profile &1 changed.
And still see the old "Date password last changed"?
Because we have an application which reported that it worked fine.
It uses CHGUSRPRF.
I even did a DSPJRN and could see all the entries EXCEPT the actual
CP entry. CP = Change Profile.
My hypothesis is that CHGUSRPRF checks before/after and doesn't
really do the change.
Once we changed his password to something else and then changed his
password it did update his password changed date.
Not that we're in the habit of gaming the system - I think we just
got hoodwinked by someone into keeping his old password.
I think I'm right.

CHGUSRPRF USRPRF(<redacted>) PASSWORD(<redacted>)

User profile <redacted> changed.

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

--
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@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
--
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@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

--
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@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com
--
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@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com


[https://www.medtronsoftware.com/img/MedtronMinilogo.bmp] Kevin Bucknum
Senior Programmer Analyst
MEDDATA / MEDTRON
120 Innwood Drive
Covington LA 70433
Local: 985-893-2550
Toll Free: 877-893-2550
https://www.medtronsoftware.com



CONFIDENTIALITY NOTICE

This document and any accompanying this email transmission contain confidential information, belonging to the sender that is legally privileged. This information is intended only for the use of the individual or entity named above. The authorized recipient of this information is prohibited from disclosing this information to any other party and is required to destroy the information after its stated need has been fulfilled. If you are not the intended recipient, or the employee of agent responsible to deliver it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or action taken in reliance on the contents of these documents is STRICTLY PROHIBITED. If you have received this email in error, please notify the sender immediately to arrange for return or destruction of these documents.
--
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@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com
--
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@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com