Auth package is crated for authenticating user for microservices. It is in beta version and I don't recomd to use it for production until the stable release.
In order to use auth package first install the package by
pip install auth-package==1.1
then import it
from auth_package import user, permission
api_key = 'test_api_e56643c8-2311-4e25-991f-03d365243f51'
email = 'test@gmail.com' first_name = 'test1' last_name = 'test2' password = 'password'
for creating user
create_user = user.create_user(email, first_name, last_name, password, api_key) user_list = user.user_list(api_key)
for authenticating user
authenticate = user.authenticate_user(email, password, api_key) print(authenticate)
1 maintainer
Metadata
1 maintainer
Release files for auth-package 1.4
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 | |
|---|---|---|---|---|
| auth_package-1.4.tar.gz | 3.4 kB | Without provenance | Details |
Release files / auth_package-1.4.tar.gz
| Download URL | auth_package-1.4.tar.gz |
|---|---|
| Size | 3.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
310587ad284877732246be9516f749257b525455c54ac013efcfbbc42bace1e0
|
|
BLAKE2b-256 checksum How to use checksums |
948de129eb50a0f41136a82a10f9a6a7e74b12de1a89e2e33841477ae21c7254
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.2
|
Security for auth-package 1.4
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.
