topic Re: expired or resetted password issue with GlobalProtect Agent 4.1.6 in General Topics

expired or resetted password issue with GlobalProtect Agent 4.1.6

DaxVC — Tue, 06 Nov 2018 09:24:17 GMT

An expired password change or a resetted password cannot be changed when using the Global Protect credential provider and PAN agent 4.1.6

I re-installed PAN agent 4.1.2 and tested this to verify if it was PAN agent related because this issue was a new feature introduced in PAN agent 4.1.
PAN agent 4.1.2 doens't have this issue

https://www.paloaltonetworks.com/documentation/41/globalprotect/globalprotect-app-new-features/new-features-released-in-gp-agent-4_1/active-directory-password-change-using-the-globalprotect-credential-provider

anyone also expiriencing this issue ?

Re: expired or resetted password issue with GlobalProtect Agent 4.1.6

BPry — Tue, 06 Nov 2018 15:46:25 GMT

@DaxVC,

I'd reach out to TAC and report the issue so that this bug actually makes it way to the proper team to get fixed.

Re: expired or resetted password issue with GlobalProtect Agent 4.1.6

DaxVC — Wed, 07 Nov 2018 13:51:48 GMT

Hi,TAC case has been openend and logs are being analyzed 🙂

Re: expired or resetted password issue with GlobalProtect Agent 4.1.6

odimitrovs — Sat, 01 Dec 2018 22:07:27 GMT

Hi,

Try upgrading to 4.1.7 as you might be experiancing:

GPC-7537
Fixed an issue on Windows 10 endpoints where, if you configured the GlobalProtect app to wrap third-party credentials, users were unable to change expired passwords using the GlobalProtect Credential Provider.

https://www.paloaltonetworks.com/documentation/41/globalprotect/globalprotect-app-release-notes/gp-app-release-information/globalprotect-app-417-addressed-issues

Thanks

Re: expired or resetted password issue with GlobalProtect Agent 4.1.6

tommyschoemans — Wed, 16 Jan 2019 12:37:36 GMT

I'm also facing this issue, did you get any usable feedback on the TAC case?

kr,

Tommy

Re: expired or resetted password issue with GlobalProtect Agent 4.1.6

DaxVC — Wed, 16 Jan 2019 13:26:41 GMT

Hi,

It had been reported that the issue is effective in GP 4.1.4 as well.

GP 4.1.2 didn't had the issue (I am not totally sure about GP 4.1.3) and that it was solved in GP 4.1.7

You may search for "GPC-7537" in the release notes of GP 4.1.7 after its announcement, to get the public notes regarding the issue. The issue had occurred because of a change in code which is related to a some kind of a "change password" flag.