Difference between revisions of "XMLRPC Protocol: getchallenge"
From Dreamwidth Notes
Foxfirefey (Talk | contribs) |
Foxfirefey (Talk | contribs) (yay dl lists) |
||
| Line 5: | Line 5: | ||
None | None | ||
== Return Values == | == 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." | + | : 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. | + | : 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. | + | : 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. | + | : The server time when the challenge was generated, as measured in seconds since the Unix epoch. |
[[Category: Protocol Documentation/XMLRPC Protocol]] | [[Category: Protocol Documentation/XMLRPC Protocol]] | ||
</noinclude> | </noinclude> | ||
Revision as of 22:13, 1 October 2009
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.
