lapa_authentication
About
Authentication service
Installation
pip install lapa_authentication
Env
- python>=3.12.0
Changelog
v0.0.20
- https support
v0.0.19
- bugfix in login and register call (update column name).
v0.0.18
- remove device entity.
- keep refresh token without hashing in database.
v0.0.17
- changed jwt token creation timezone to utc.
- handled token expiry exception while decoding token.
v0.0.16
- update repo link in setup.py
- keep version numbers for square_logger and lapa_database_structure as >= instead of ~=.
- add SQUARE_LOGGER and LAPA_DATABASE_HELPER sections in config and initialise their sdk as per those variables.
v0.0.15
- add new call for /logout.
v0.0.14
- add new call for /generate_access_token.
v0.0.13
- add custom message and status code for duplicate username.
- delete session if already present on same device for same user.
- encrypt mac_address in login and register.
- keep seperate secret keys for access token refresh token and mac address encrpytion.
v0.0.12
- create entry in device table and user_session_device table for login and register.
v0.0.11
- changes in login and register calls as per database structure changes (naming convention)
v0.0.10
- changes in register calls w.r.t new table Credential
v0.0.9
- fix missing dependencies in setup.py
v0.0.8
- remove salt storing from register.
- implement login route.
v0.0.7
- overhaul register logic.
- overhaul tablename import logic.
v0.0.6
- syntax error fix in main.py.
v0.0.5
- update database tables.
- move reading of database tables to configuration.py.
v0.0.4
- bug fix - add "email_validator>=2.0.0" in dependencies.
v0.0.3
- use lapa_commons to read config.
v0.0.2
- move logger to configuration.py.
- remove unused dependencies.
- add lapa_database_helper.
v0.0.1
- /register endpoint added.
- Before adding user into the authentication server. It will first check if the user's email-id is already present
in the database or not.
- If Yes -> Do not create entry in the database. Return message saying user already exists.
- If No -> Create entry in the database. Return message saying user created successfully.
- Before adding user into the authentication server. It will first check if the user's email-id is already present
in the database or not.
Metadata
Release files for lapa-authentication 0.0.20
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 |
|---|---|---|---|---|
| lapa_authentication-0.0.20.tar.gz | 8.7 kB | Without provenance | Details for lapa_authentication-0.0.20.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| lapa_authentication-0.0.20-py3-none-any.whl | Python 3 | none | any | Details for lapa_authentication-0.0.20-py3-none-any.whl |
Total release size: 18.5 kB
Release files / lapa_authentication-0.0.20.tar.gz
| Download URL | lapa_authentication-0.0.20.tar.gz |
|---|---|
| Size | 8.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c3b90cfc2d0b324e1abf1479f2a201f3ed60bd7c7279a1080992515d5ba9100e
|
|
BLAKE2b-256 checksum How to use checksums |
7a20b8f56d122d113c36050110b6e8c2b25f733df4eeb55e560eac3b254f75ef
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.9.19
|
Release files / lapa_authentication-0.0.20-py3-none-any.whl
| Download URL | lapa_authentication-0.0.20-py3-none-any.whl |
|---|---|
| Size | 9.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
53edd92575d3d39213a253d471abb52159bb0df0aa223013abde22e6c0f67bdc
|
|
BLAKE2b-256 checksum How to use checksums |
b39030d366a83c5f1180c9232aa173b80480eabe8824f17d0fba5b557e14937b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.9.19
|
Security for lapa-authentication 0.0.20
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.