Add the ip address of the ASA on the ACS which is 192.168.1.4 and shared secret key which is CISCO123:
Creating a rule in Default Network Access policy
1.select an identity store (means define whether users are internal to ACS or in external database)
2. Authorization policy: (allowing permit or deny access)
Test with CLI:
You can use the test command on the command line in order to test your AAA setup. A test request is sent to the AAA server, and the result appears on the command line.
ciscoasa#test aaa-server authentication RADIUS host 192.168.1.2
username cisco password cisco123INFO: Attempting Authentication test to IP address <192.168.1.2>
(timeout: 12 seconds)
INFO: Authentication Successful
Run the following command to see the debugs:
#Debug aaa common 255
ACS 5.5 secondary registration - Registration failed due to Invalid Certificate
When you enable Trust Communication on your primary and secondary ACS instance, and you register the secondary instance with the primary, both the primary and secondary instance check the CA and server certificates of each other. After the certificates are verified: – If the certificates in both the primary and secondary ACS instances are valid certificates, the instances establish a secure tunnel between them and register the secondary instance to the primary.
I don't think it supports self-signed certificate however you can try installing the self-signed certificate of Primary in the secondary instance CA store and self signed certificate of secondary in the primary instance CA store.
Please post comments if there are any queries and rate if useful.