05-17-2023 03:03 AM
Customer have one ISE and five AD domains which have zero trust between. I'm able to join the ISE to all five ADs and created the identity source sequence from top AD1 to bottom AD5.
Any different of time taken to authenticate between user from AD1 and AD5? Is it in millisecond? Customer want to know how long it take and document it.
Solved! Go to Solution.
05-21-2023 06:06 PM
@williamtan For active directory, it's preferred to use scopes so the ISE will query all AD join points the same time.
It's hard to judge the authentication time because it depends on both ISE and AD servers. AD servers could be busy and slower in responses.
05-17-2023 04:28 AM
Hi @williamtan ,
1st please take a look at Administration > Identity Management > Identity Source Sequences > select your Sequence Name and make sure that at Advanced Search List Settings, the Treat as if the user was not found and proceed to the next store in the sequence is selected.
2nd at Administration > System > Settings > Protocols > RADIUS > check the value of Highlight steps longer than (millisenconds).
3rd at Operations > Reports > Reports > Endpoint and Users > RADIUS Authentications > click the Details icon > at the new windows you are able to check the Steps of the RADIUS Authentication and check the 24325 Resolving Identity, if this step takes longer than the value of Highlight steps longer than (millisenconds), then you have your answer in an exact number.
Hope this helps !!!
05-17-2023 09:12 PM
Thank you Marcelo Morais for your fast reply.
1. Yes, I have select this already.
2. This one is default 1000 milliseconds.
3. I didn't see a clock there so it should be less than 1000ms.
05-18-2023 04:58 AM
05-19-2023 06:10 AM
Hi Marcelo Morais ,
I try to change the value of Highlight steps longer than to 500ms and it still not show the time. But customer want to know the exact time. Is it possible?
05-19-2023 11:14 AM
Hi @williamtan ,
at Operations > Troubleshooting > Diagnostic Tools > General Tools > TCP Dump:
Download and open the TCPDump.pcap file via Wireshark and filter by: tcp.port == 389. (for example), you are able to check the Time between packets exchange.
Hope this helps !!!
05-21-2023 06:06 PM
@williamtan For active directory, it's preferred to use scopes so the ISE will query all AD join points the same time.
It's hard to judge the authentication time because it depends on both ISE and AD servers. AD servers could be busy and slower in responses.
05-22-2023 10:07 PM
Hi @hslai,
Do I still need to select "Treat as if the user was not found and proceed to the next store in the sequence" after use the initial scope?
05-23-2023 10:26 AM
We may use the Active Directory scope directly as the identity authentication source. That setting is for an ISE identity source sequence so it would not be in effect unless we are using one when we combine the Active directory scope with other other sources.
05-24-2023 07:43 AM - edited 05-24-2023 07:45 AM
Hi @hslai , let me investigate the "scope" configuration you are mentioning.
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