monkdev/monk-id

Integrate Monk ID authentication and single sign-on for apps and websites on the server-side.

Monk ID PHP

, _(*1)

Integrate Monk ID authentication and single sign-on for apps and websites on the server-side., _(*2)

• Documentation

Overview

Install

Using Composer, add monkdev/monk-id to your composer.json:, _(*3)

{
  "require": {
    "monkdev/monk-id": "~1.0"
  }
}

$ composer update

Or:, _(*4)

$ composer require monkdev/monk-id:~1.0

Configure

Configuration is done in an external INI file. There's a sample file in this repository: config/monkId.sample.yml. Copy this file to your codebase, then load the config in your code during initialization:, _(*5)

Monk\Id::loadConfig('/path/to/monkId.ini', 'development');

Remember, replace the sample values with your own, and keep the file safe as it contains your app secret., _(*6)

Access

If you have Monk ID JS configured to store the payload automatically in a cookie (the default), you can skip the next part as the cookie is also loaded automatically., _(*7)

If not, the encoded payload can be passed directly, which is useful if you're sending it in a GET/POST request instead:, _(*8)

Monk\Id::loadPayload($monkIdPayload);

Loading the payload must be done before trying to access any values stored in the payload. In an MVC framework, this usually means placing it in a method in your ApplicationController that's executed before the specific action is processed., _(*9)

Once the payload is loaded, you can ask whether the user is logged in:, _(*10)

Monk\Id::loggedIn()

Or for their ID and email:, _(*11)

Monk\Id::userId()
Monk\Id::userEmail()

null is returned if the user isn't logged in or the payload can't be decoded and verified., _(*12)

Development

Composer is used for dependency management and task running. Start by installing the dependencies:, _(*13)

$ composer install

Tests

Testing is done with PHPUnit. To run the tests:, _(*14)

$ composer test

Continuous integration is setup through Travis CI to run the tests against PHP v5.6, v7.0, and v7.1. (Circle CI is also setup to run the tests against PHP v5.6, but is backup for now until multiple versions can easily be specified.) The code coverage results are sent to Coveralls during CI for tracking over time. Badges for both are dispayed at the top of this README., _(*15)

While the test suite is complete, it's not a bad idea to also test changes manually in real-world integrations., _(*16)

Documentation

phpDocumentor is used for code documentation. To build:, _(*17)

$ composer phpdoc

This creates a doc directory (that is ignored by git)., _(*18)

Quality

A number of code quality tools are configured to aid in development. To run them all at once:, _(*19)

$ composer quality

Each tool can also be run individually:, _(*20)

• php -l: $ composer phplint
• PHP_CodeSniffer: $ composer phpcs
• PHP Copy/Paste Detector: $ composer phpcpd
• PHPLOC: $ composer phploc
• PHP Mess Detector: $ composer phpmd
• SensioLabs Security Checker: $ composer security-checker

Deployment

Publishing a release to Packagist simply requires creating a git tag:, _(*21)

$ git tag -a vMAJOR.MINOR.PATCH -m "Version MAJOR.MINOR.PATCH"
$ git push origin vMAJOR.MINOR.PATCH

Be sure to choose the correct version by following Semantic Versioning., _(*22)

Publish Documentation

After releasing a new version, the documentation must be manually built and published to the gh-pages branch., _(*23)