Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Recently our higher changed the name of our DC's and didn't let us know until after the fact. As a result we are not able to log into our On-Prem server. "Your username and/or password does not match our records, kindly try again. If the problem pe...
Hello,I have not been able to find a solution to my problem. Hopefully someone will be able to assist or point me in the right direction.I am needing to use RADIUS as my SSH authentication using an ISE server running 3.1 and is FIPS enabled. So, TAC...
I have set up VPN certificate authentication/authorization on an ASA5520. I am not having any problems with the authentication part, but, I am having an issue with authorization. Users get authorization through LDAP to our AD network, however, we h...
@Rodrigo Diaz , I have looked into the STIG requirement to have FIPS enabled on the ISE server. If you don't have it enabled on the ISE server but configure a FIPS 140-2/3 validated HMAC or other FIPS 140-2/3 approved methods, the finding is lowered...
Thanks @Rodrigo Diaz for the update. I was getting the picture that it wasn't going to be possible.What are some alternatives to get authentication working with FIPS enabled devices?
Solved the problem. The configuration of the ldap-base-dn statement under the aaa-server policy was not pointing at a high enough OU level. Once I changed it users were able to connect.
