This is a pre-production deployment of Warehouse, however changes made here WILL affect the production instance of PyPI.
Latest Version Dependencies status unknown Test status unknown Test coverage unknown
Project Description

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
Release History

Release History

1.0

This version

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

Download Files

Download Files

TODO: Brief introduction on what you do with files - including link to relevant help section.

File Name & Checksum SHA256 Checksum Help Version File Type Upload Date
msisdn-cli-1.0.tar.gz (5.7 kB) Copy SHA256 Checksum SHA256 Source Feb 3, 2015

Supported By

WebFaction WebFaction Technical Writing Elastic Elastic Search Pingdom Pingdom Monitoring Dyn Dyn DNS HPE HPE Development Sentry Sentry Error Logging CloudAMQP CloudAMQP RabbitMQ Heroku Heroku PaaS Kabu Creative Kabu Creative UX & Design Fastly Fastly CDN DigiCert DigiCert EV Certificate Rackspace Rackspace Cloud Servers DreamHost DreamHost Log Hosting