Hi,
We're running into another issue in production. SSO (Vintela, Tomcat, AD 2003 authentication) works just fine if users access the website within their own desktops in the network. Now, when they take their laptops home, and enter into the network via VPN, SSO doesn't work. Now, I suspect that when users enter into the network through the VPN, (Juniper HTTPS SSL + RSA Security Token), that mechanism creates a Kerberos ticket that is different from when I log on to my computer within the network. I do know a Kerberos ticket is created, however, because users that come in to the network via VPN can access IIS just fine, but not the the VSJ application. But going about troubleshooting this will be difficult. Where should I start, or better yet, what could I do to alleviate the issue? (Choose the least path of disturbance, since VPN is being used for over 1000 users). I could always create a Terminal Server, and have VPN users RDP to that server first and access the website there. However, that is just a workaround....Is there anyting on the Vintela end that I can tweak to make this work? BTW, the Tomcat logs show nothing....
Thanks for any help.
Moogeboo