comparison doc/auth-protocol.txt @ 4099:0c11f0b05e19 HEAD

Fixed outdated information: ssl-valid-cert -> valid-client-cert
author Timo Sirainen <timo.sirainen@movial.fi>
date Tue, 07 Mar 2006 16:10:36 +0200
parents e2fe8222449d
children bc071307fc2a
comparison
equal deleted inserted replaced
4098:59883de6c516 4099:0c11f0b05e19
101 - lip=<local ip> : Local IP - in standard string format, 101 - lip=<local ip> : Local IP - in standard string format,
102 - rip=<remote ip> : Remote IP - ie. for IPv4 127.0.0.1 and for IPv6 ::1 102 - rip=<remote ip> : Remote IP - ie. for IPv4 127.0.0.1 and for IPv6 ::1
103 - resp=<base64> : Initial response for authentication mechanism 103 - resp=<base64> : Initial response for authentication mechanism
104 - secured : Remote user has secured transport to auth client 104 - secured : Remote user has secured transport to auth client
105 (eg. localhost, SSL, TLS) 105 (eg. localhost, SSL, TLS)
106 - ssl-valid-cert : Remote user has presented a valid SSL certificate. 106 - valid-client-cert : Remote user has presented a valid SSL certificate.
107 107
108 FAIL parameters may contain "reason=.." parameter which should be sent to 108 FAIL parameters may contain "reason=.." parameter which should be sent to
109 remote user instead of a standard "Authentication failed" message. For 109 remote user instead of a standard "Authentication failed" message. For
110 example "invalid base64 data". It should NOT be used to give exact reason 110 example "invalid base64 data". It should NOT be used to give exact reason
111 for authentication failure (ie. "user not found" vs. "password mismatch"). 111 for authentication failure (ie. "user not found" vs. "password mismatch").