Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit 85d0ced

Browse files
authored
Merge pull request auth0#260 from auth0/fix-readme
Fix README
2 parents 86e5c7d + f8ce56f commit 85d0ced

File tree

1 file changed

+23
-21
lines changed

1 file changed

+23
-21
lines changed

README.rst

Lines changed: 23 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -12,24 +12,24 @@ Installation
1212

1313
You can install the auth0 Python SDK using the following command.
1414

15-
.. code-block::
15+
.. code-block:: python
1616
1717
pip install auth0-python
1818
1919
For python3, use the following command
2020

21-
.. code-block::
21+
.. code-block:: python
2222
2323
pip3 install auth0-python
2424
25-
Python 3.2 and 3.3 have reached `EOL <https://en.wikipedia.org/wiki/CPython#Version_history>`_ and support will be removed in the near future.
25+
Python 3.2 and 3.3 have reached `EOL <https://en.wikipedia.org/wiki/CPython#Version_history>`__ and support will be removed in the near future.
2626

2727
========================
2828
Authentication SDK Usage
2929
========================
3030

3131
The Authentication SDK is organized into components that mirror the structure of the
32-
`API documentation <https://auth0.com/docs/auth-api>`_.
32+
`API documentation <https://auth0.com/docs/auth-api>`__.
3333
For example:
3434

3535
.. code-block:: python
@@ -67,16 +67,17 @@ If you need to authenticate a user using their email and password, you can use t
6767
ID Token validation
6868
===================
6969
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>`__.
7171
7272
Before you access its contents, you must verify that the ID token has not been tampered with and that it is meant for your application to consume. The ``TokenVerifier`` class can be used to perform this verification.
7373
7474
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.
7875
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>`__.
8081
8182
For asymmetric algorithms like RS256, use the ``AsymmetricSignatureVerifier`` class, passing
8283
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
178179
Management SDK Usage
179180
====================
180181
181-
To use the management library you will need to instantiate an Auth0 object with 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 object with 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:
182183
183184
.. code-block:: python
184185
@@ -264,7 +265,7 @@ Which returns something like this
264265
Success!
265266
266267
All endpoints follow a similar structure to ``connections``, and try 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>`__.
268269
269270
==============
270271
Error Handling
@@ -274,8 +275,9 @@ When consuming methods from the API clients, the requests could fail for a numbe
274275
- Invalid data sent as part of the request: An ``Auth0Error` is raised with the error code and description.
275276
- Global or Client Rate Limit reached: A ``RateLimitError`` is raised and the time at which the limit
276277
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.
278279
280+
==================================
279281
Available Authentication Endpoints
280282
==================================
281283
@@ -288,7 +290,7 @@ Available Authentication Endpoints
288290
- API Authorization - Get Token ( ``authentication.GetToken``)
289291
- API Authorization - Authorization Code Grant (``authentication.AuthorizeClient``)
290292
291-
293+
==============================
292294
Available Management Endpoints
293295
==============================
294296
@@ -320,36 +322,36 @@ Available Management Endpoints
320322
Change Log
321323
==========
322324
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>`__.
324326
325327
===============
326328
Issue Reporting
327329
===============
328330
329331
If you have found a bug or if you have a feature request, please report them at this repository issues section.
330332
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.
332334
333335
==============
334336
What is Auth0?
335337
==============
336338
337339
Auth0 helps you to:
338340
339-
* Add authentication with `multiple authentication sources <https://auth0.com/docs/identityproviders>`_,
341+
* Add authentication with `multiple authentication sources <https://auth0.com/docs/identityproviders>`__,
340342
either social like **Google, Facebook, Microsoft Account, LinkedIn, GitHub, Twitter, Box, Salesforce, among others**,
341343
or enterprise identity systems like **Windows Azure AD, Google Apps, Active Directory, ADFS or any SAML Identity Provider**.
342-
* Add authentication through more traditional `username/password databases <https://auth0.com/docs/connections/database/mysql>`_.
343-
* Add support for `linking different user accounts <https://auth0.com/docs/link-accounts>`_ with the same user.
344-
* Support for generating signed `JSON Web Tokens <https://auth0.com/docs/jwt>`_ to call your APIs and **flow the user identity** securely.
344+
* Add authentication through more traditional `username/password databases <https://auth0.com/docs/connections/database/mysql>`__.
345+
* Add support for `linking different user accounts <https://auth0.com/docs/link-accounts>`__ with the same user.
346+
* Support for generating signed `JSON Web Tokens <https://auth0.com/docs/jwt>`__ to call your APIs and **flow the user identity** securely.
345347
* Analytics of how, when and where users are logging in.
346-
* Pull data from other sources and add it to the user profile, through `JavaScript rules <https://auth0.com/docs/rules>`_.
348+
* Pull data from other sources and add it to the user profile, through `JavaScript rules <https://auth0.com/docs/rules>`__.
347349
348350
===========================
349351
Create a free Auth0 Account
350352
===========================
351353
352-
1. Go to `Auth0 <https://auth0.com/>`_ and click Sign Up.
354+
1. Go to `Auth0 <https://auth0.com/>`__ and click Sign Up.
353355
2. Use Google, GitHub or Microsoft Account to log in.
354356
355357
=======

0 commit comments

Comments
 (0)