In this video we will integrate Azure AD with Identity Services as an external identity and build policy using ROPC. We will test out the configuration and validate the results - we will also test out an example connecting to Azure AD using EAP-TTLS as a condition while still access AD using other protocols. Note: I am using ISE 3.1 and if using ISE 3.0 you will need to update a root CA from MS on ISE - this is not required for ISE 3.1. Also, this check out the caveats when using ROPC and EAP-TTLS.
Another comment around authZ policies - if you have other policies beyond users in AAD you want to add additional conditions to further maximize performance - so in my example you can also tie EAP-TTLS or Network Access:AuthenticationIdentityStore for AAD and perhaps PEAP etc. for AD. Again, this is to reduce latency and increase performance.
Негізгі бет Cisco Identity Services Engine: 802.1X and Azure AD using ROPC (EAP-TTLS)
No video
Пікірлер: 11