fyle-django-allauth
Fyle OAuth 2.0 provider for django-allauth, lets you associate Fyle accounts with your User accounts.
Dependencies
Install django-allauth and configure it.
Quick start
-
Install fyle-django-allauth
pip install fyle-django-allauth -
Include 'fyle_allauth' in the INSTALLED_APPS section of settings.py :
INSTALLED_APPS = ( ... 'django.contrib.sites', 'allauth', 'allauth.account', 'allauth.socialaccount', 'fyle_allauth' # new -
Fyle App registration (get your client_id and client_secret here)
- Login to Fyle
- Goto settings and click on Developers
- Click on create new app, enter the details and select type as OAuth 2.0
- For Redirect URI enter
- 'http://localhost:8000/accounts/fyle/login/callback/' for development
- 'https://your_domain/accounts/fyle/login/callback/' for production
- Note down the client_secret and client_id
-
Open django-admin and create a new record under Social Applications Select Fyle as provider and enter the above noted client_secret and client_id.
Final step is to add our site to the Chosen sites on the bottom.
-
Visit http://localhost:8000/accounts/fyle/login to login using your Fyle account.
-
If using a custom user model then add the below lines to settings.py
# For custom user model that has email as the user identifying field ACCOUNT_USER_MODEL_USERNAME_FIELD = None ACCOUNT_USERNAME_REQUIRED = False ACCOUNT_EMAIL_REQUIRED = True ACCOUNT_AUTHENTICATION_METHOD = 'email' # Disable verification mail [optional] ACCOUNT_EMAIL_VERIFICATION = 'none' -
If you are using a different application then update your base URL by adding the below line to settings.py
FYLE_BASE_URL = 'https://app.fyle.in'
For more info on customisation refer the django-allauth documentation
Metadata
Release files for fyle-django-allauth 0.1.2
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 | Actions |
|---|---|---|---|---|
| fyle-django-allauth-0.1.2.tar.gz | 4.6 kB | Without provenance | Details for fyle-django-allauth-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| fyle_django_allauth-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for fyle_django_allauth-0.1.2-py3-none-any.whl |
Total release size: 10.4 kB
Release files / fyle-django-allauth-0.1.2.tar.gz
| Download URL | fyle-django-allauth-0.1.2.tar.gz |
|---|---|
| Size | 4.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3fffaadd2260c3d35924047084eee10bfbcc8221d1595ac59396ec92848f2ab4
|
|
BLAKE2b-256 checksum How to use checksums |
3fe5e3a34c4da95a53005be37df192a1abf59a2e0372e53b039a1c6dc794fe84
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/40.8.0 requests-toolbelt/0.9.1 tqdm/4.43.0 CPython/3.7.4
|
Release files / fyle_django_allauth-0.1.2-py3-none-any.whl
| Download URL | fyle_django_allauth-0.1.2-py3-none-any.whl |
|---|---|
| Size | 5.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b26779113c9f5e834cdbfa1f010fe67f8ebea4c940eca39c9024d97cfce6f692
|
|
BLAKE2b-256 checksum How to use checksums |
3ad51cf4450a3a1d93f427c6d9f3e561896e62305292fb46671706f4a74b31c3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/40.8.0 requests-toolbelt/0.9.1 tqdm/4.43.0 CPython/3.7.4
|
Security for fyle-django-allauth 0.1.2
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.