Skip to content

Latest commit

 

History

History
151 lines (96 loc) · 6.03 KB

README.md

File metadata and controls

151 lines (96 loc) · 6.03 KB
Raw

Keycloak Auth Service

This folder contains the configuration and code for the Keycloak service.

Overview

We are using a customised version of the Keycloak standalone server for user identity and access management (IdAM).

We're using the GOV.UK theme for Keycloak (forked from the original theme maintained by the Home Office).

Running locally

In most cases, there is no need to run keycloak from this repo. However, there is docker compose file which setups everything in such case.

Getting Setup

This project includes git submodules, so when running git clone you need to add the --recurse-submodules option. If you have already pulled, you can run git submodule init and then git submodule update --recursive instead. You might also need to run git submodule update --recursive if the submodule is updated because of a pull.

This assumes you've followed the setup steps in the root README.

Visit the Keycloak admin console on http://keycloak:8080/auth/admin (default credentials can be found here)

Note that the addition of a "keycloak" entry to the hosts file (as described in the the root README) is needed because the website Docker container and host browser need to access Keycloak on the same hostname (due to the requirement that access tokens must be issued and validated on the same hostname).

Deployment

Keycloak is automatically deployed to the relevant environment by Travis CI, as described in the root README.

Deployment from scratch

Login to GOV.UK PaaS and set the relevant space as described in the cosmetics README.

Database

To create a Keycloak database for the current space:

cf marketplace -s postgres
cf enable-service-access postgres
cf create-service postgres small-10.5 keycloak-database

Keycloak

Start by setting up the following credentials:

  • To configure Notify for email and SMS sending (see the GOV.UK Notify account section in the root README to get this value):

    cf cups keycloak-notify-env -p '{ "NOTIFY_API_KEY": "XXX", "NOTIFY_SMS_TEMPLATE_ID": "XXX" }'

Once all the credentials are created, the app can be deployed using:

SPACE=<<space>> ./keycloak/deploy.sh

Initial configuration

When deploying Keycloak from scratch, an initial configuration file is imported on first launch, which creates a default admin user for the master realm, creates and configures the PSD realm and associated client, and creates a default test user account for logging into the PSD website.

The relevant login credentials can be found in the accounts section of the root README.

IMPORTANT: You should follow the instructions below to change the admin password and client secret from their default values.

Log into the Keycloak administration console using the default admin credentials.

Set a strong password for the master admin account:

  • Select realm > Master > Users > View all users
  • Edit the admin user > Credentials
  • Enter and confirm the new password, disable the 'Temporary' option, and click 'Reset Password'

Setup clients

The instructions in this sections are given for the PSD client, but should be repeated for Cosmetics and all other clients required.

Generate a new client secret for the PSD app:

  • Select realm > OPSS > Clients > psd-app > Credentials > Regenerate Secret

Create the client credentials for the PSD app:

cf cups psd-keycloak-env -p '{
    "KEYCLOAK_AUTH_URL": "https://<<keycloak domain>>/auth",
    "KEYCLOAK_CLIENT_ID": "psd-app",
    "KEYCLOAK_CLIENT_SECRET": "XXX"
}'

(The client secret is listed on the Keycloak admin console: Clients > psd-app > Credentials)

Allow keycloak to redirect back to the app after login

  • Select realm > OPSS > Clients > psd-app
  • Add https://<<PSD domain>>/* to the Valid Redirect URIs section and click save
  • Replace all localhost values with https://<<PSD domain>>/

Follow the steps in the SMS autheticator README's Configuration section to enable SMS two factor authentication. Set the 2FA code length to 6.

Setup event logging

Setup the system out event listener:

  • Select Events > Config
  • Add "system-out" to the "Event Listeners" section

Troubleshooting

Problem: the keycloak database doesn't exist when running $ docker-compose up

Error message:

WARN  [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (ServerService Thread Pool -- 52) IJ000604: Throwable while attempting to get a new connection: null: javax.resource.ResourceException: IJ031084: Unable to create connection
[......]
Caused by: org.postgresql.util.PSQLException: FATAL: database "keycloak" does not exist

The first time $ docker-compose up is run in the root directory, a keycloak database is created according to /postgres/setup-keycloak.sh. This database shares a docker volume with the dev database.

If the local keycloak database is subsequently dropped but the development database is not, then this script will not run the next time you run $ docker-compose up.

To recreate the database, start the postgres command line with

$ docker-compose exec postgres --username keycloak

then in the postgres interface run each command from /postgres/setup-keycloak.sh.

Problem: blank page after logging in to admin console in cloud keycloak

In such case, there is problem with cloud router. Make sure you have forwarded headers properly:

cf update-service my-cdn-route \
    -c '{"headers": ["Accept", "Authorization"]}'

https://docs.cloud.service.gov.uk/deploying_services/use_a_custom_domain/#amend-the-service