| commit | efce16caf238c239a11090f30ba53f7af1bafb27 | |
| author | Stefan Becker <chemobejk@gmail.com> | |
| Wed, 7 Dec 2011 14:55:38 +0000 (7 16:55 +0200) | ||
| committer | Stefan Becker <chemobejk@gmail.com> | |
| Wed, 7 Dec 2011 14:55:38 +0000 (7 16:55 +0200) | ||
| tree | a1fca5454bb2b80801c9c529244c7a4ffbe6d9e2 | treesnapshot (tar.gz zip) |
| parent | c93c6ab7679227d6ca87ddb9f4cf6eb3015111ae | commitdiff |
tlsdsk: clean up user/login name usage
Inside WSDL requests and the certificate we have to use the user name,
e.g. first.last@domain.com or sip:first.last@domain.com.
For the HTTP authentication handshake in the WinNegotiate authentication
we need to use the standard domain/login user combination, i.e.
DOMAIN\login. If the login user is empty, we use the user name as usual,
e.g. DOMAIN\first.last@domain.com.
Inside WSDL requests and the certificate we have to use the user name,
e.g. first.last@domain.com or sip:first.last@domain.com.
For the HTTP authentication handshake in the WinNegotiate authentication
we need to use the standard domain/login user combination, i.e.
DOMAIN\login. If the login user is empty, we use the user name as usual,
e.g. DOMAIN\first.last@domain.com.