Authserver

Authserver is an OAuth2-based single-signon authentication provider written in PHP.

Authserver is the central hub that stores and provides user accounts and user-specific data to other services that require this data.

Its primary usecase is handling the authentication for all webbased applications within one organisation, but security controls allow to expose limited access to other organisations.

License

Authserver is licensed under the terms of the GNU Affero General Public License, either version 3 of the License, or (at your option) any later version.

See the LICENSE.md file for a full copy of the license.

Installation

Download

Releases can be downloaded from the releases page, or by checking out a tag from this repository.

Configuration

Create an app/config/parameters.yml from the app/config/parameters.yml.dist template and fill in the applicable configuration parameters.

Dependencies

PHP dependencies are handled by composer, these can be installed with a single SYMFONY_ENV=prod composer install --no-dev -o inside the project root.

To compile the bootstrap stylesheets, less is required. Less runs on node.js, so install that one first. Then run npm install inside the project root to install less.

Then run the following commands to prepare the database and assets.

php app/console assets:install --env=prod
php app/console assetic:dump --env=prod
php app/console braincrafted:bootstrap:install --env=prod
php app/console doctrine:migrations:migrate --env=prod

Creating the first user

Without any users, authserver is not really useful, so let's add our first user. (Who will be a super-admin to manage the application.)

php app/console app:adduser --super-admin $username $password $email --env=prod

If you ever happen to forget your password, you can set a new one with php app/console app:passwd $username $new_password --env=prod.

Publishing the application

Only the web/ directory should be publicly accessible, all requests that do not match a file in the web/ directory should be rewritten to web/app.php by the webserver. How to accomplish this depends on your webserver, but a .htaccess file that accomplishes this is present in the web/ folder.

Upgrading

Upgrading can be done easily by overwriting the old files with a fresh copy. (If you have cloned the repository, just git fetch and check out the newer tag.)

Next, execute the same commands as when installing the dependencies.

Deployment tool

An automated deployment tool is available as ./deploy.sh.

It automatically puts the application in maintenance mode, pulls the latest version of the current branch and rebases local commits on top of it.

WARNING: When an automatic pull and rebase fails, you will be dropped to a shell to fix the situation. If you have local changes, you can run the following commands to try to fix the situation.

git stash git pull --rebase git stash pop exit

> Because this will result in untested changes, it is recommended to keep your own repository with the necessary
> changes and merge releases to this repository instead of deploying directly from the master repository.

It then handles the updating dependencies, assets and database migrations.
When all these steps have completed successfully, the maintenance mode is disabled, and the new version of the application
is deployed.

#### Advanced usage

The deployment tool has a number of flags to change its default behavior:

* `-n, --no-pull`: Does not pull a new version from the repository
* `--skip-maintenance`: Skips manipulations of the maintenance mode
* `-e <env>, --env=<env>`: Changes the symfony environment to run all commands in
* `-s, --shell`: Starts a shell instead of running any update commands
* `-l, --lock-maintenance`: Puts the application in maintenance mode. This maintenance mode will only be disabled by running the matching `--unlock-maintenance` command.
* `-u, --unlock-maintenance`: Disables the maintenance mode