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.
Hi everyone,I am currently troubleshooting an authorization issue with Cisco ISE 3.5 Patch 4 and Microsoft Entra ID joined devices using EAP-TLS authentication.The authentication process completes successfully, and ISE is able to communicate with Mic...
When applying a patch to Cisco ISE nodes in a distributed deployment, after patching the Primary Administration Node (PAN), should the Secondary Administration Node (Secondary PAN) be patched next, followed by the PSNs? Or, if patching one node at a ...
Is it recommended to perform a direct upgrade from ISE 3.3 Patch 11 to ISE 3.5, and can a backup taken from an ISE 3.3 deployment be successfully restored to a node running ISE 3.5? I’m aware that the official ISE upgrade path indicates this is suppo...
I have an issue I hope someone could help me with. I am having an issue with 802.1x authentication on ISE. They are using PEAP with certificate computer only authentication and everything appears to be configured correctly but authentication continue...
I am trying to use the fiber connections on the SNS 3700 but I am unable to ping the appliance. The ip address is configured on the appliance on port 0 but the appliance is shown to be connected to the switch on port 2. Is this correct or is there so...
Yes, I’m aware. I also tried configuring it using the device name as both the CN and DNS value in the device certificate, but I was still unable to get the authorization to succeed but thanks for the info.
The attributes in the certificate are the following: Subject name format = CN={{AAD_Device_ID}},OU=EAD_Client and the Subject alternatvie name is DNS = {{DeviceName}}