Difference between revisions of "XMLRPC Protocol: getchallenge"

From Dreamwidth Notes
Redirect page
Jump to: navigation, search
(Created page with '<noinclude>Category: Protocol DocumentationCategory: Protocol Documentation/XMLRPC Protocol == Description ==</noinclude> Generate a one-time, quick expiration challenge …')
 
 
(11 intermediate revisions by 3 users not shown)
Line 1: Line 1:
<noinclude>[[Category: Protocol Documentation]][[Category: Protocol Documentation/XMLRPC Protocol]]
+
#REDIRECT [[XML-RPC_Protocol_Method:_getchallenge]]
== Description ==</noinclude>
+
Generate a one-time, quick expiration challenge to be used in challenge/response authentication methods.<noinclude>
+
== Arguments ==
+
None
+
== Return Values ==
+
* auth_scheme
+
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
+
An opaque cookie to generate a hashed response from.
+
* expire_time
+
The expiration time of the challenge, as measured in seconds since the Unix epoch.
+
* server_time
+
The server time when the challenge was generated, as measured in seconds since the Unix epoch.
+

Latest revision as of 20:17, 7 December 2010