GitHub

Cloud CMS provides integrated authentication and single-sign-on (SSO) with GitHub.

This page describes the authentication provider available for the Cloud CMS Application Server that enables your mobile or web applications as well as the Cloud CMS user interface or API to authenticate against GitHub.

For more information, see our documentation on the general Authentication / SSO framework.

API Keys

You will need to configure a GitHub application and have the following information available:

  • clientID - the GitHub App ID
  • clientSecret - the GitHub App secret

Examples

Here is a simple configuration where we provide our API Keys and fallback on the defaults for everything else.

"auth": {
    "enabled": true,
    "providers": {
        "twitter": {
            "enabled": true,
            "clientID": "{GitHub App ID}",
            "clientSecret": "{GitHub App Secret}"
        }
    }
}

Here is another example where we redirect to the error.html page if the user failed to log in. We also set things up so that a user account will be created automatically if a user couldn't be found for the authenticated GitHub user.

"auth": {
    "enabled": true,
    "providers": {
        "twitter": {
            "enabled": true,
            "successRedirect": "/index.html",
            "failureRedirect": "/error.html",
            "clientID": "{GitHub App ID}",
            "clientSecret": "{GitHub App Secret}"
            "autoRegister": true
        }
    }
}