We are using the DN of a user's certificate to identify them in the system.
This makes for a better user experience once they have installed their
certificates. But having the backing services have to parse the DN just to
get something readable is annoying at the least. But the way things are
movin
Hello!
On Mon, Feb 13, 2017 at 10:19:36AM -0500, Alex Addy wrote:
> While testing the new $ssl_client_s_dn variable (as of 1.11.6) I discovered
> that it doesn't handle unicode characters correctly, Say if I had a user
> cert with a DN of 'CN=доверенная третья сторона' after going through nginx
>
While testing the new $ssl_client_s_dn variable (as of 1.11.6) I discovered
that it doesn't handle unicode characters correctly, Say if I had a user
cert with a DN of 'CN=доверенная третья сторона' after going through nginx
it becomes 'CN=\D0\B4\D0\BE\D0\B2\D0\B5\D1\80\D0\B5\D0\BD\D0\BD\D0\B0\D1\8F
