parameters
oauthlib.oauth2.rfc6749.parameters ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This module contains methods related to Section 4
_ of the OAuth 2 RFC.
.. _Section 4
: https://tools.ietf.org/html/rfc6749#section-4
parse_authorization_code_response(uri, state=None)
Parse authorization grant response URI into a dict.
If the resource owner grants the access request, the authorization server issues an authorization code and delivers it to the client by adding the following parameters to the query component of the redirection URI using the application/x-www-form-urlencoded
format:
code REQUIRED. The authorization code generated by the authorization server. The authorization code MUST expire shortly after it is issued to mitigate the risk of leaks. A maximum authorization code lifetime of 10 minutes is RECOMMENDED. The client MUST NOT use the authorization code more than once. If an authorization code is used more than once, the authorization server MUST deny the request and SHOULD revoke (when possible) all tokens previously issued based on that authorization code. The authorization code is bound to the client identifier and redirection URI.
state REQUIRED if the "state" parameter was present in the client authorization request. The exact value received from the client.
:param uri: The full redirect URL back to the client. :param state: The state parameter from the authorization request.
For example, the authorization server redirects the user-agent by sending the following HTTP response:
.. code-block:: http
HTTP/1.1 302 Found
Location: https://client.example.com/cb?code=SplxlOBeZQQYbYS6WxSbIA
&state=xyz
Source code in server/vendor/oauthlib/oauth2/rfc6749/parameters.py
233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 |
|
parse_implicit_response(uri, state=None, scope=None)
Parse the implicit token response URI into a dict.
If the resource owner grants the access request, the authorization server issues an access token and delivers it to the client by adding the following parameters to the fragment component of the redirection URI using the application/x-www-form-urlencoded
format:
access_token REQUIRED. The access token issued by the authorization server.
token_type REQUIRED. The type of the token issued as described in Section 7.1. Value is case insensitive.
expires_in RECOMMENDED. The lifetime in seconds of the access token. For example, the value "3600" denotes that the access token will expire in one hour from the time the response was generated. If omitted, the authorization server SHOULD provide the expiration time via other means or document the default value.
scope OPTIONAL, if identical to the scope requested by the client, otherwise REQUIRED. The scope of the access token as described by Section 3.3.
state REQUIRED if the "state" parameter was present in the client authorization request. The exact value received from the client.
:param uri: :param state: :param scope:
Similar to the authorization code response, but with a full token provided in the URL fragment:
.. code-block:: http
HTTP/1.1 302 Found
Location: http://example.com/cb#access_token=2YotnFZFEjr1zCsicMWpAA
&state=xyz&token_type=example&expires_in=3600
Source code in server/vendor/oauthlib/oauth2/rfc6749/parameters.py
289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 |
|
parse_token_response(body, scope=None)
Parse the JSON token response body into a dict.
The authorization server issues an access token and optional refresh token, and constructs the response by adding the following parameters to the entity body of the HTTP response with a 200 (OK) status code:
access_token REQUIRED. The access token issued by the authorization server. token_type REQUIRED. The type of the token issued as described in Section 7.1
. Value is case insensitive. expires_in RECOMMENDED. The lifetime in seconds of the access token. For example, the value "3600" denotes that the access token will expire in one hour from the time the response was generated. If omitted, the authorization server SHOULD provide the expiration time via other means or document the default value. refresh_token OPTIONAL. The refresh token which can be used to obtain new access tokens using the same authorization grant as described in Section 6
. scope OPTIONAL, if identical to the scope requested by the client, otherwise REQUIRED. The scope of the access token as described by Section 3.3
_.
The parameters are included in the entity body of the HTTP response using the "application/json" media type as defined by [RFC4627
_]. The parameters are serialized into a JSON structure by adding each parameter at the highest structure level. Parameter names and string values are included as JSON strings. Numerical values are included as JSON numbers. The order of parameters does not matter and can vary.
:param body: The full json encoded response body. :param scope: The scope requested during authorization.
For example:
.. code-block:: http
HTTP/1.1 200 OK
Content-Type: application/json
Cache-Control: no-store
Pragma: no-cache
{
"access_token":"2YotnFZFEjr1zCsicMWpAA",
"token_type":"example",
"expires_in":3600,
"refresh_token":"tGzv3JOkF0XG5Qx2TlKWIA",
"example_parameter":"example_value"
}
.. Section 7.1
: https://tools.ietf.org/html/rfc6749#section-7.1 .. Section 6
: https://tools.ietf.org/html/rfc6749#section-6 .. Section 3.3
: https://tools.ietf.org/html/rfc6749#section-3.3 .. RFC4627
: https://tools.ietf.org/html/rfc4627
Source code in server/vendor/oauthlib/oauth2/rfc6749/parameters.py
358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 |
|
prepare_grant_uri(uri, client_id, response_type, redirect_uri=None, scope=None, state=None, code_challenge=None, code_challenge_method='plain', **kwargs)
Prepare the authorization grant request URI.
The client constructs the request URI by adding the following parameters to the query component of the authorization endpoint URI using the application/x-www-form-urlencoded
format as defined by [W3C.REC-html401-19991224
_]:
:param uri: :param client_id: The client identifier as described in Section 2.2
. :param response_type: To indicate which OAuth 2 grant/flow is required, "code" and "token". :param redirect_uri: The client provided URI to redirect back to after authorization as described in Section 3.1.2
. :param scope: The scope of the access request as described by Section 3.3
. :param state: An opaque value used by the client to maintain state between the request and callback. The authorization server includes this value when redirecting the user-agent back to the client. The parameter SHOULD be used for preventing cross-site request forgery as described in Section 10.12
. :param code_challenge: PKCE parameter. A challenge derived from the code_verifier that is sent in the authorization request, to be verified against later. :param code_challenge_method: PKCE parameter. A method that was used to derive the code_challenge. Defaults to "plain" if not present in the request. :param kwargs: Extra arguments to embed in the grant/authorization URL.
An example of an authorization code grant authorization URL:
.. code-block:: http
GET /authorize?response_type=code&client_id=s6BhdRkqt3&state=xyz
&code_challenge=kjasBS523KdkAILD2k78NdcJSk2k3KHG6&code_challenge_method=S256
&redirect_uri=https%3A%2F%2Fclient%2Eexample%2Ecom%2Fcb HTTP/1.1
Host: server.example.com
.. W3C.REC-html401-19991224
: https://tools.ietf.org/html/rfc6749#ref-W3C.REC-html401-19991224 .. Section 2.2
: https://tools.ietf.org/html/rfc6749#section-2.2 .. Section 3.1.2
: https://tools.ietf.org/html/rfc6749#section-3.1.2 .. Section 3.3
: https://tools.ietf.org/html/rfc6749#section-3.3 .. _section 10.12
: https://tools.ietf.org/html/rfc6749#section-10.12
Source code in server/vendor/oauthlib/oauth2/rfc6749/parameters.py
25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 |
|
prepare_token_request(grant_type, body='', include_client_id=True, code_verifier=None, **kwargs)
Prepare the access token request.
The client makes a request to the token endpoint by adding the following parameters using the application/x-www-form-urlencoded
format in the HTTP request entity-body:
:param grant_type: To indicate grant type being used, i.e. "password", "authorization_code" or "client_credentials".
:param body: Existing request body (URL encoded string) to embed parameters into. This may contain extra parameters. Default ''.
:param include_client_id: True
(default) to send the client_id
in the body of the upstream request. This is required if the client is not authenticating with the authorization server as described in Section 3.2.1
_. :type include_client_id: Boolean
:param client_id: Unicode client identifier. Will only appear if include_client_id
is True. *
:param client_secret: Unicode client secret. Will only appear if set to a value that is not None
. Invoking this function with an empty string will send an empty client_secret
value to the server. *
:param code: If using authorization_code grant, pass the previously obtained authorization code as the code
argument. *
:param redirect_uri: If the "redirect_uri" parameter was included in the authorization request as described in Section 4.1.1
_, and their values MUST be identical. *
:param code_verifier: PKCE parameter. A cryptographically random string that is used to correlate the authorization request to the token request.
:param kwargs: Extra arguments to embed in the request body.
Parameters marked with a *
above are not explicit arguments in the function signature, but are specially documented arguments for items appearing in the generic **kwargs
keyworded input.
An example of an authorization code token request body:
.. code-block:: http
grant_type=authorization_code&code=SplxlOBeZQQYbYS6WxSbIA
&redirect_uri=https%3A%2F%2Fclient%2Eexample%2Ecom%2Fcb
.. _Section 4.1.1
: https://tools.ietf.org/html/rfc6749#section-4.1.1
Source code in server/vendor/oauthlib/oauth2/rfc6749/parameters.py
93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 |
|
prepare_token_revocation_request(url, token, token_type_hint='access_token', callback=None, body='', **kwargs)
Prepare a token revocation request.
The client constructs the request by including the following parameters using the application/x-www-form-urlencoded
format in the HTTP request entity-body:
:param token: REQUIRED. The token that the client wants to get revoked.
:param token_type_hint: OPTIONAL. A hint about the type of the token submitted for revocation. Clients MAY pass this parameter in order to help the authorization server to optimize the token lookup. If the server is unable to locate the token using the given hint, it MUST extend its search across all of its supported token types. An authorization server MAY ignore this parameter, particularly if it is able to detect the token type automatically.
This specification defines two values for token_type_hint
:
* access_token: An access token as defined in [RFC6749],
`Section 1.4`_
* refresh_token: A refresh token as defined in [RFC6749],
`Section 1.5`_
Specific implementations, profiles, and extensions of this
specification MAY define other values for this parameter using the
registry defined in `Section 4.1.2`_.
.. Section 1.4
: https://tools.ietf.org/html/rfc6749#section-1.4 .. Section 1.5
: https://tools.ietf.org/html/rfc6749#section-1.5 .. _Section 4.1.2
: https://tools.ietf.org/html/rfc7009#section-4.1.2
Source code in server/vendor/oauthlib/oauth2/rfc6749/parameters.py
175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 |
|
validate_token_parameters(params)
Ensures token presence, token type, expiration and scope in params.
Source code in server/vendor/oauthlib/oauth2/rfc6749/parameters.py
445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 |
|