# JunoPass Python Support
Implementation of [JunoPass Authentication](https://developers.junopass.com/junopass-api/authenticating-users) API in Python.
## Installation
pip install junopass-py –upgrade
## Get access token and project id
Create an account for access token and project id - https://console.junopass.com
## How to setup device
Note the private_key must never be shared.
from junopass import JunoPass
jp = JunoPass(<Access-Token>, <JunoPass-Public-Key>, <Project-ID>) private_key, public_key = jp.setup_device()
## Authenticating user - step 1
Submit authentication details to JunoPass. Verify signed challenge hash for authenticity.
method = “EMAIL” identifier = “testuser@example.com”
valid_challenge, device_id, login_request = jp.authenticate(method, identifier, pubkey)
## Verify account using challenge and OTP token - step 2
Verify OTP message. Send back the user OTP plus a valid challenge obtained in step 1 i.e authenticate function. This function also checks the returned response for authenticity.
resp = jp.verify(valid_challenge, device_id, prvtkey, otp=120104) print(resp)
## Run Test
python -m unittest
Metadata
Release files for junopass-py 1.0.9
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 | |
|---|---|---|---|---|
| junopass-py-1.0.9.tar.gz | 3.8 kB | Without provenance | Details |
Release files / junopass-py-1.0.9.tar.gz
| Download URL | junopass-py-1.0.9.tar.gz |
|---|---|
| Size | 3.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5175bfeb5eca669b6adc34cd15257b891ab32dab1ac1823ab967271519e2486e
|
|
BLAKE2b-256 checksum How to use checksums |
4bb6d9a8c5217a87e4ed038c03453ea36956b91c50fdebed18b091549b6cb59c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Python-urllib/3.6
|
Security for junopass-py 1.0.9
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.