06-04-2018 12:19 PM
Hello,
is it possible to use same ISE as primary and secondary authentication server (using different identity source) in tunnel-group config?
For exmaple first authentication against ISE internal database and second against Radius Token server...
Thanks for answers.
Peter
06-04-2018 12:59 PM
And I forgot to mention that username is same for both authentications
06-05-2018 06:24 AM
Hi,
I had an internal conversation about this and don't believe this is a supported configuration because we don't see a way for ISE be the first authentication then set itself as the token server. You would need another token server for this configuration to work properly.
Regards,
-Tim
06-05-2018 07:13 AM
Hi Tim,
we have setup:
ASA -- ISE -- Gemalto OTP server
And idea was use ISE server as a single point of contact from ASA. For both primary and secondary authentication.
primary - ISE internal database
secondary - Gemalto OTP with ISE as Radius "proxy"
Username will be the same for both identities.
If ASA be able to send some Radius attributes to ISE for recognition between primary and secondary authentication....
Then ISE can use this attribute for Identity Store selection
06-07-2018 04:38 PM
ISE at present supports two dual authentications -- EAP Chaining and CWA Chaining. Neither applies to VPN. The likely options for you are:
1. Continuing with ASA doing two authentications -- first to OTP and 2nd to ISE
2. Using ISE but OTP for auth and Internal Users for authorization.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide