Difference between revisions of "XMLRPC Protocol: getchallenge"
From Dreamwidth Notes
| Line 1: | Line 1: | ||
{{#set:name=getchallenge|type=Challenge/Response}} | {{#set:name=getchallenge|type=Challenge/Response}} | ||
| + | |||
== Description == | == Description == | ||
| + | |||
[[Description::Generate a one-time, quick expiration challenge to be used in challenge/response authentication methods.]] | [[Description::Generate a one-time, quick expiration challenge to be used in challenge/response authentication methods.]] | ||
| + | |||
== Arguments == | == Arguments == | ||
| − | None | + | |
| + | None. | ||
| + | |||
== Return Values == | == Return Values == | ||
| + | |||
; auth_scheme '''string''' | ; auth_scheme '''string''' | ||
: You can ignore this for now. By default this is the highest version of our authentication schemes, if in the future if we implement other auth schemes or change the default. In that case we'd add a new capabilities exchange: Your client could say, "I know c0 and c1", and our server would then say, "Use c1, it's the best." | : You can ignore this for now. By default this is the highest version of our authentication schemes, if in the future if we implement other auth schemes or change the default. In that case we'd add a new capabilities exchange: Your client could say, "I know c0 and c1", and our server would then say, "Use c1, it's the best." | ||
| Line 13: | Line 19: | ||
; server_time '''integer''' | ; server_time '''integer''' | ||
: The server time when the challenge was generated, as measured in seconds since the Unix epoch. | : The server time when the challenge was generated, as measured in seconds since the Unix epoch. | ||
| − | [[Category: Protocol Documentation | + | |
| + | [[Category: Protocol Documentation]] | ||
| + | [[Category: XML-RPC Protocol]] | ||
Revision as of 20:06, 7 December 2010
Description
Generate a one-time, quick expiration challenge to be used in challenge/response authentication methods.
Arguments
None.
Return Values
- auth_scheme string
- You can ignore this for now. By default this is the highest version of our authentication schemes, if in the future if we implement other auth schemes or change the default. In that case we'd add a new capabilities exchange: Your client could say, "I know c0 and c1", and our server would then say, "Use c1, it's the best."
- challenge string
- An opaque cookie to generate a hashed response from.
- expire_time integer
- The expiration time of the challenge, as measured in seconds since the Unix epoch.
- server_time integer
- The server time when the challenge was generated, as measured in seconds since the Unix epoch.
