You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm accessing domain resources over VPN from a local user account that isn't domain-associated (yet) and doesn't have the same username as my AD user. (Recently joined a company, this is the interim setup.)
ADPassMon doesn't offer to set a username. But it does offer to refresh a kerberos ticket, and when I do so and enter my password, it comes up with an expiration time in the year when Hamlet is believed to have been first performed, and a password expiry timeout of -151180 days.
The text was updated successfully, but these errors were encountered:
Oh, just noticed that this issue is known for a long time now, in comments from 2011 in https://yourmacguy.wordpress.com/adpassmon/ — still worth registering it here, I guess. Will ADPassMon still work if it just sends the correct domain account name, or must the user account be domain-associated?
I'm actually preparing to hand over the reins of ADPassMon development to macmule. He has a fork in active development. I'm pretty much only doing bigfixes at this point, and yours is a new feature request.
I'm accessing domain resources over VPN from a local user account that isn't domain-associated (yet) and doesn't have the same username as my AD user. (Recently joined a company, this is the interim setup.)
ADPassMon doesn't offer to set a username. But it does offer to refresh a kerberos ticket, and when I do so and enter my password, it comes up with an expiration time in the year when Hamlet is believed to have been first performed, and a password expiry timeout of -151180 days.
The text was updated successfully, but these errors were encountered: