You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -67,16 +67,17 @@ If you need to authenticate a user using their email and password, you can use t
67
67
ID Token validation
68
68
===================
69
69
70
-
Upon successful authentication, the credentials received may include an ``id_token``, if the authentication request contained the ``openid`` scope. The ``id_token`` contains information associated with the authenticated user. You can read more about ID tokens `here <https://auth0.com/docs/tokens/concepts/id-tokens>`_.
70
+
Upon successful authentication, the credentials received may include an ``id_token``, if the authentication request contained the ``openid`` scope. The ``id_token`` contains information associated with the authenticated user. You can read more about ID tokens `here <https://auth0.com/docs/tokens/concepts/id-tokens>`__.
71
71
72
72
Before you access its contents, you must verify that the ID token has not been tampered withand that it is meant for your application to consume. The ``TokenVerifier``class can be used to perform this verification.
73
73
74
74
To create a ``TokenVerifier``, the following arguments are required:
75
-
* A ``SignatureVerifier`` instance, which is responsible for verifying the token's algorithm name and signature.
76
-
* The expected issuer value, which typically matches the Auth0 domain prefixed with``https://``and suffixed with``/``.
77
-
* The expected audience value, which typically matches the Auth0 application client ID.
78
75
79
-
The type of ``SignatureVerifier`` used depends upon the signing algorithm used by your Auth0 application. You can view this value in your application settings under ``Advanced settings | OAuth | JsonWebToken Signature Algorithm``. Auth0 recommends using the RS256 asymmetric signing algorithm. You can read more about signing algorithms `here <https://auth0.com/docs/tokens/signing-algorithms>`_.
76
+
- A ``SignatureVerifier`` instance, which is responsible for verifying the token's algorithm name and signature.
77
+
- The expected issuer value, which typically matches the Auth0 domain prefixed with``https://``and suffixed with``/``.
78
+
- The expected audience value, which typically matches the Auth0 application client ID.
79
+
80
+
The type of ``SignatureVerifier`` used depends upon the signing algorithm used by your Auth0 application. You can view this value in your application settings under ``Advanced settings | OAuth | JsonWebToken Signature Algorithm``. Auth0 recommends using the RS256 asymmetric signing algorithm. You can read more about signing algorithms `here <https://auth0.com/docs/tokens/signing-algorithms>`__.
80
81
81
82
For asymmetric algorithms like RS256, use the ``AsymmetricSignatureVerifier``class, passing
82
83
the public URL where the certificates for the public keys can be found. This will typically be your Auth0 domain with the ``/.well-known/jwks.json`` path appended to it. For example, ``https://your-domain.auth0.com/.well-known/jwks.json``.
@@ -178,7 +179,7 @@ The ID of the invitation and organization are available as query parameters on t
178
179
Management SDK Usage
179
180
====================
180
181
181
-
To use the management library you will need to instantiate an Auth0 objectwith a domain and a `Management API v2 token <https://auth0.com/docs/api/management/v2/tokens>`_. Please note that these token last 24 hours, so if you need it constantly you should ask for it programmatically using the client credentials grant with a `non interactive client <https://auth0.com/docs/api/management/v2/tokens#1-create-and-authorize-a-client>`_ authorized to access the API. For example:
182
+
To use the management library you will need to instantiate an Auth0 objectwith a domain and a `Management API v2 token <https://auth0.com/docs/api/management/v2/tokens>`__. Please note that these token last 24 hours, so if you need it constantly you should ask for it programmatically using the client credentials grant with a `non interactive client <https://auth0.com/docs/api/management/v2/tokens#1-create-and-authorize-a-client>`__ authorized to access the API. For example:
182
183
183
184
.. code-block:: python
184
185
@@ -264,7 +265,7 @@ Which returns something like this
264
265
Success!
265
266
266
267
All endpoints follow a similar structure to ``connections``, andtry to follow as
267
-
closely as possible the `API documentation <https://auth0.com/docs/api/v2>`_.
268
+
closely as possible the `API documentation <https://auth0.com/docs/api/v2>`__.
268
269
269
270
==============
270
271
Error Handling
@@ -274,8 +275,9 @@ When consuming methods from the API clients, the requests could fail for a numbe
274
275
- Invalid data sent as part of the request: An ``Auth0Error` is raised with the error code and description.
275
276
- Global or Client Rate Limit reached: A ``RateLimitError`` is raised and the time at which the limit
276
277
resets is exposed in the ``reset_at``property. When the header is unset, this value will be ``-1``.
277
-
- Network timeouts: Adjustable by passing a ``timeout`` argument to the client. See the `rate limit docs <https://auth0.com/docs/policies/rate-limits>`_for details.
278
+
- Network timeouts: Adjustable by passing a ``timeout`` argument to the client. See the `rate limit docs <https://auth0.com/docs/policies/rate-limits>`__for details.
278
279
280
+
==================================
279
281
Available Authentication Endpoints
280
282
==================================
281
283
@@ -288,7 +290,7 @@ Available Authentication Endpoints
288
290
-API Authorization - Get Token ( ``authentication.GetToken``)
289
291
-API Authorization - Authorization Code Grant (``authentication.AuthorizeClient``)
290
292
291
-
293
+
==============================
292
294
Available Management Endpoints
293
295
==============================
294
296
@@ -320,36 +322,36 @@ Available Management Endpoints
320
322
Change Log
321
323
==========
322
324
323
-
Please see `CHANGELOG.md <https://github.com/auth0/auth0-python/blob/master/CHANGELOG.md>`_.
325
+
Please see `CHANGELOG.md <https://github.com/auth0/auth0-python/blob/master/CHANGELOG.md>`__.
324
326
325
327
===============
326
328
Issue Reporting
327
329
===============
328
330
329
331
If you have found a bug orif you have a feature request, please report them at this repository issues section.
330
332
Please do not report security vulnerabilities on the public GitHub issue tracker.
331
-
The `Responsible Disclosure Program <https://auth0.com/whitehat>`_ details the procedure for disclosing security issues.
333
+
The `Responsible Disclosure Program <https://auth0.com/whitehat>`__ details the procedure for disclosing security issues.
0 commit comments