When setting up a Global policy object for a Paloalto globalprotect user/group , the maxpwdage attribute does not match the, the password expiry date sent for Paloalto user, This can be confusing to know when the password actually going to expire for the GP user.
AD server 2012r2
Max password age was set on 14.05.17
Tailing the authd logs whilst connecting with a GP user
>>tail follow yes mp-logs authd
It shows that there are only 64 days left before the password expires, however the default domain policy is set to 75 days
This difference is due to the attirbutes maxpwdage an pwdlastset were set on differnet date.
run the below command on windows shell
get-aduser -filter * -properties passwordlastset, passwordneverexpires |ft Name, passwordlastset, Passwordneverexpires
The output below suggests that passwordlast set for the user on 04.05.17
There is a difference of 11 days between attributes maxpwdage and pwdlastset
maxpwdage-passwordlast set= password expiry
75 -11 =64 days
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!