@capevace/single-sign-on

Single Sign On

Simple auth server used by Mission Control

Installation

$ npm install -g @capevace/single-sign-on

Usage

You can now start the server like you would any binary.

$ single-sign-on --version
v0.2.0

Options

Usage: single-sign-on [options]

Options:
  -V, --version         output the version number
  -u, --url <url>       the url SSO is reachable at
  -p, --port <port>     the port to use for the http server
  --hash-pw <password>  hash a password to put in config
  -h, --help            display help for command

Config

A config file for mission-control will be created at $HOME_DIR/.mission-control-sso/config. This can also be used to configure mission-control. However, options passed as command line arguments override settings in this file.

Default Credentials

Username: admin

Password: admin

Changelog

Version 0.3.0

• Changed config location from .mission-control-sso to .single-sign-on
• Minor fixes

Version 0.2.0

• Added support for server to be proxied. Mission Control now does this by default.

Authors

Lukas Mateffy – @Capevace – mateffy.me

Distributed under the MIT license. See LICENSE for more information.

Contributing

1. Fork it (https://github.com/capevace/mission-control/fork)
2. Create your feature branch (git checkout -b feature/fooBar)
3. Commit your changes (git commit -am 'Add some fooBar')
4. Push to the branch (git push origin feature/fooBar)
5. Create a new Pull Request