I've been having issues with NAC AD SSO. The AD SSO service is started on both my CAS's in the CAS pair, and I do see that the Clean Access Agent attempts to perform AD SSO. But it fails and defaults to prompting for a local username and password. After which, I see the following event recorded in the CAS's logs:
Oct 17, 2008 1:46:45 PM com.perfigo.wlan.jmx.admin.GSSServer$LoginPrivilegedAction run SEVERE: Error opening server socket. Socket closed
If the AD SSO service started on the CAS but the users are failing AD SSO, I would start with confirming the user is logging into the domain and not using cached credentials. AD SSO using the users kerberos ticket to authenticate
Load the MS kerbtray utility and confirm a valid kerberos ticket is present (icon will be green).
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...