On 10/18/2022 10:00, Tobias Brunner wrote:
Hi Karl,
Yes, as documented on [1], the Windows client uses the CN value as
EAP identity with EAP-TLS (i.e. user certificates). I didn't know
this can actually be changed, so that might be something we could
add to the docs. Could you provide deta
Hi Karl,
And, it appears, Windows is insisting on using the CN when presenting
the identity (instead of the field(s) in the SAN) unless you set the
option on the VPN profile to allow an override -- and then you have
to hand-key it on each connection. I don't believe there is any way
to tell