The goal of this project is to have a reusable component that allow us to authenticate against a microservice for user management. This will take the JWT token that was send in the request Authorization header and it will use it to retrieve the user information and store it in the local user database.
Quick start
Install the project by doing pip install authconnector
Install the usual django migrations.
- Add the app to the django INSTALLED_APPS:
‘remoteauth’
Add the next configuration on the django settings:
INMOBILIO_AUTHENTICATION_SERVICE = { ‘JWT_VALIDATION_URL’: ‘http://localhost:9000/auth/user’ }
Done :D
You can now retrieve the user within the request to your API endpoints.
1 maintainer
Metadata
1 maintainer
Release files for authconnector 1.0.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 | |
|---|---|---|---|---|
| authconnector-1.0.1.tar.gz | 3.8 kB | Without provenance | Details |
Release files / authconnector-1.0.1.tar.gz
| Download URL | authconnector-1.0.1.tar.gz |
|---|---|
| Size | 3.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
31a4c83426a74f9a6b644f7ee589a431ef60b92a17051ff76fe576e2ed9b0b4b
|
|
BLAKE2b-256 checksum How to use checksums |
a0c2dd1de8759ba9ed8086d8df8d4928a86e185ad4d95db5741b921810abcb34
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.18.4 setuptools/40.8.0 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.7.1
|
Security for authconnector 1.0.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.
