msisdn-cli
This little CLI tool let you validate both MT and MOMT flow using MSISDN server.
To start a MT Flow:
msisdn-cli -H https://msisdn.services.mozilla.com \
-c 310 -n +1xxxxxxxxxxx
To start a MOMT Flow:
msisdn-cli -H https://msisdn.services.mozilla.com -c 310
You can also create a certificate to then try to register on a Service Provider such as Loop.
To do so add an –audience parameter and a –login-endpoint you can also provide some –data or –json to be POST with your registration request:
msisdn-cli -H https://msisdn.services.mozilla.com -c 310 -n +1xxxxxxxxxxx \
--audience https://loop.services.mozilla.com
--login-endpoint https://loop.services.mozilla.com/registration
--json '{"simplePushURL": "http://httpbin.org/deny"}'
If you want you can just display the cURL command using –dry-run:
msisdn-cli -H https://msisdn.services.mozilla.com -c 310 -n +1xxxxxxxxxxx \
--audience https://loop.services.mozilla.com
--login-endpoint https://loop.services.mozilla.com/registration
--json '{"simplePushURL": "http://httpbin.org/deny"}' --dry-run
The msisdn-cli script will then build you an assertion and write down a curl command to run to make sure it works.
You can also use the -v, –verbose command to display the assertion.
You should get a 200 OK status code with a Hawk-Session-Token header.
If not, here are the error messages you can get:
- “Certificate expired”: you play too long with this curl command,
ask for a new certificate
- “Invalid audience”: The Service Provider doesn’t accept this audience
It can be either a misconfiguration on the server or you trying the assertion to a wrong server.
- “Issuer not trusted”: The MSISDN server that generate your certificate
is not trusted on this Service Provider. It can be either a misconfiguration or you trying the assertion to a wrong server.
Something else? Please make a PR to add it here.
Don’t forget to use msisdn-cli -h to get more help.
INSTALL
make install source .venv/bin/activate
Metadata
Release files for msisdn-cli 1.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 |
|---|---|---|---|---|
| msisdn-cli-1.0.tar.gz | 5.7 kB | Without provenance | Details for msisdn-cli-1.0.tar.gz |
Release files / msisdn-cli-1.0.tar.gz
| Download URL | msisdn-cli-1.0.tar.gz |
|---|---|
| Size | 5.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e2d7bc9c12e2cbf8f97fadd934f974eef6d442103fe70b07f3cd0bf811f43715
|
|
BLAKE2b-256 checksum How to use checksums |
97373923daa6cba250914a1792a9a8ac343fc9f1bbec1717f849e31122713b38
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for msisdn-cli 1.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.