Upsonic Auth
The cloud authentication save system for your python applications ! Control everything from one place and distribute all clients without effort.
Installation
You can install Upsonic by pip3:
pip3 install upsonic_auth
Implementing
1) Encrypted and Free Version
We suggest to use in your individual projects because this way not provide any control process so everyone can add credientials.
*Creating Your Free Cloud Key
Upsonic cloud_key
from upsonic_auth import Upsonic_Auth
auth = Upsonic_Auth("YOUR_ENCRYPTION_KEY", "YOUR_CLOUD_KEY")
auth.add_user("Name", "Pass")
#auth.delete_user("Name")
if auth.check("name", "Pass"): # In another.py, Diffferent Machine, Different Environment
print("Verified")
2) Encrypted and Pro Version
We suggest to use in your individual projects because this way not provide any control process so everyone can add credientials.
*For this you should have Upsonic Cloud Pro
from upsonic_auth import Upsonic_Auth_Pro
auth = Upsonic_Auth_Pro("YOUR_ENCRYPTION_KEY", "YOUR_CLOUD_PRO_KEY", "YOUR_ACCESS_KEY")
auth.add_user("Name", "Pass")
#auth.delete_user("Name")
if auth.check("name", "Pass"): # In another.py, Diffferent Machine, Different Environment
print("Verified")
3) Encrypted and Secure Version
You can free for all purposes.
*For this you should have Upsonic Cloud Dedicated
from upsonic_auth import Upsonic_Auth_Dedicated
auth = Upsonic_Auth_Dedicated("YOUR_ENCRYPTION_KEY", "YOUR_DATABASE_NAME", "YOUR_ADMIN_PASSWORD", "YOUR_DEDICATED_KEY")
auth.add_user("Name", "Pass")
#auth.delete_user("Name")
auth = Upsonic_Auth_Dedicated("YOUR_DATABASE_NAME", "YOUR_USER_PASSWORD", "YOUR_DEDICATED_KEY")
if auth.check("name", "Pass"): # In another.py, Diffferent Machine, Different Environment and CUSTOMER
print("Verified")
Contributing
Contributions to Upsonic Auth are welcome! If you have any suggestions or find a bug, please open an issue on the GitHub repository. If you want to contribute code, please fork the repository and create a pull request.
License
Upsonic Auth is released under the MIT License.
Contributors
Thank you for your contribution!
1 maintainer
Metadata
1 maintainer
Release files for upsonic-auth 0.2.0
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 |
|---|---|---|---|---|
| upsonic_auth-0.2.0.tar.gz | 3.7 kB | Without provenance | Details for upsonic_auth-0.2.0.tar.gz |
Release files / upsonic_auth-0.2.0.tar.gz
| Download URL | upsonic_auth-0.2.0.tar.gz |
|---|---|
| Size | 3.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f2ca344ae0fc4480ac1cafea6067d0d748f51fa641cded377d0f5cb4e468b707
|
|
BLAKE2b-256 checksum How to use checksums |
113a9c2a5c4750c01a976cb60fd5c5e28dd85d2129f8f081e5389bfe7e8ac8ae
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.18
|
Security for upsonic-auth 0.2.0
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.
