Got a server running ACS v3.3 talking to a SecurID ACE server. When I set a user up to use SecurID, ACS always reports "CS user unknown" - when the user is plainly in the database. If I change user back to use Internal auth - it works a treat.
If tried using the "Unknown user policy" to force all requests to SecurID - this works OK - but doesn't collect any attributes from the users account in ACS.
v3.1 seems to work fine - is there a bug with v3.3 ?
Interesting, did the external db config for RSA come from 3.1, ie you just installed 3.3 over 3.1? If so you could try deleting the securid config and re-creating. But I admit thats a long shot
If things work when you enable the unknown user policy.... does it create totally new users in parallel to the ones already there?
To get "CS user unknown" it means ACS looked in its DB and didnt find a user with the same name. I would set logging to max (under system config) run the test again and then look in the CSAuth log file (under CSAuth/logs.auth.log) Look for "starting authentication for" type messages. That will give a good idea as to what is going on.
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...