Django Azure AD Auth
======================
*Django Azure AD Auth* allows you to authenticate through Azure Active Directory.
Installation
------------
Run `pip install django-azure-ad-auth`
Add the `AzureActiveDirectoryBackend` to your `AUTHENTICATION_BACKENDS` setting:
```python
AUTHENTICATION_BACKENDS = (
...
'azure_ad_auth.backends.AzureActiveDirectoryBackend',
)
```
Settings
--------
###AAD_TENANT_ID
The Azure Tenant ID. It can be found in the URL of the Azure Management Portal.
###AAD_CLIENT_ID
The Azure Application Client ID.
###AAD_AUTHORITY
**default:** `'https://login.microsoftonline.com'`
The domain that is used for authorization, the federation metadata document, and loggin out.
###AAD_SCOPE
**default:** `'openid'`
OAuth scope parameter.
###AAD_RESPONSE_TYPE
**default:** `'id_token'`
Tells OAuth to return a JWT token in its response.
###AAD_RESPONSE_MODE
**default:** `'form_post'`
Defines how the response parameters are returned. Valid choices are `fragment` or `form_post`.
###AAD_USER_CREATION
**default:** `True`
Allow creation of new users after successful authentication.
======================
*Django Azure AD Auth* allows you to authenticate through Azure Active Directory.
Installation
------------
Run `pip install django-azure-ad-auth`
Add the `AzureActiveDirectoryBackend` to your `AUTHENTICATION_BACKENDS` setting:
```python
AUTHENTICATION_BACKENDS = (
...
'azure_ad_auth.backends.AzureActiveDirectoryBackend',
)
```
Settings
--------
###AAD_TENANT_ID
The Azure Tenant ID. It can be found in the URL of the Azure Management Portal.
###AAD_CLIENT_ID
The Azure Application Client ID.
###AAD_AUTHORITY
**default:** `'https://login.microsoftonline.com'`
The domain that is used for authorization, the federation metadata document, and loggin out.
###AAD_SCOPE
**default:** `'openid'`
OAuth scope parameter.
###AAD_RESPONSE_TYPE
**default:** `'id_token'`
Tells OAuth to return a JWT token in its response.
###AAD_RESPONSE_MODE
**default:** `'form_post'`
Defines how the response parameters are returned. Valid choices are `fragment` or `form_post`.
###AAD_USER_CREATION
**default:** `True`
Allow creation of new users after successful authentication.
Metadata
Release files for django-azure-ad-auth 1.3.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| django-azure-ad-auth-1.3.1.tar.gz | 5.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_azure_ad_auth-1.3.1-py2-none-any.whl | Python 2 | none | any | Details |
Total release size: 12.8 kB
Release files / django-azure-ad-auth-1.3.1.tar.gz
| Download URL | django-azure-ad-auth-1.3.1.tar.gz |
|---|---|
| Size | 5.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
defd670f973c3c8c8516e4e88d80b5a58f28be649609323affe4f03a7dd4da04
|
|
BLAKE2b-256 checksum How to use checksums |
8a9366f6c3546dc1460d0477ef53d7f36d4870bc8ed45a98e550f50be6118bb6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / django_azure_ad_auth-1.3.1-py2-none-any.whl
| Download URL | django_azure_ad_auth-1.3.1-py2-none-any.whl |
|---|---|
| Size | 7.1 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
b94fadb4c74dfbb35f7af152bc6eee77ff617b19d13b601d1acf69c77ae47b63
|
|
BLAKE2b-256 checksum How to use checksums |
d1af7969bb6fa513c2a1b6a991a080c1d78c7fbea5ab6f7c9c598738d2fdbd8d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-azure-ad-auth 1.3.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.