We ran into what looks like the same issue in our environment, except we're using machine certificates instead of user certs. Our setup: Identity is set to SAN:DNS Our SCEP profile adds a SAN DNS attribute with the value {{DeviceName}}.mydomain.local When the issue started, the username in Access Manager logs changed from COMPUTERNAME.domain.local to host/COMPUTERNAME.domain.local, and authentication started failing. The issue lasted about 24 hours, then resolved on its own, host/ disappeared and authentication started working again without any config changes on our end. I had opened a support case but didn't receive any helpful information, so we were in the dark as to what happened until I found this post. I also haven’t found any documentation confirming whether machine cert-based EAP-TLS is officially supported with Access Manager. Glad it’s working again, but wondering: Was this caused by a backend change that they rolled back or a bug that they fixed? Is our setup (machine certs + SAN:DNS) officially supported? Should we deploy a fallback WLAN to our devices in case this happens again or is there another workaround anyone can suggest? Thanks
... View more