How long does ironport wsa cache ad credentials at a workstation?

[keithsauer507]

Here is an issue.

Say a person logs onto a workstation with limited internet access.  Almost all internet sites are blocked per company policy.  They log off the computer and another individual logs into the workstation.  This individual should have internet access with a different policy.  However the Ironport still thinks the last person is logged in, so they cannot access anything on the internet.

How do you circumvent this issue?

We have an S160 running 7.5.2-304 and we are a Microsoft Windows organization.

Under Security Services > End User Notification, we redirect the blocked notification page to a custom one on another server/ironport/stop.asp.  We had to remove the reauthenticate user button because either it wouldn't always come up anyway, or we would get http 500 server errors.  So how else can I reauthenticate the user?

[Ken Stieers]

There is an issue (bug? Weirdness with how MS stuff works) when you RDP to a box and login.

Since the current RDP client actually checks with AD before it lets you connect to the other machine, your local machine shows up as the account you RDP'd with, NOT your account. (because the most recent login from that IP was the account...)

I have this issue when I rdp to servers with service accounts...

Your users, who don't have/use multiple accounts won't see this issue.