keycloakb

README

Keycloak bridge

The keycloak bridge has two purposes. All our interactions (administration) with keycloak pass through it, and keycloak sends all events (i.e. login, user creation,...) to the bridge, so that they can be processed, stored,...

The service includes logging, metrics, tracing, and error tracking. The logs are written to stdout. Metrics such as time tracking,... are collected and saved to an InfluxDB Time Series Database. Jaeger is used for distributed tracing and error tracking is managed with Sentry.

Build

The service uses FlatBuffers for data serialisation. Make sure you have FlatBuffers installed and up to date with flatc --version. It was tested with "flatc version 1.8.0 (Nov 22 2017)".

Build the service for the environment <env>:

./scripts/build.sh --env <env>

Note: <env> is used for versioning.

Container

The keycloak bridge is intended to run in a container with keycloak (including the event-emitter module). See the repository keycloak-service.

Configuration

Configuration is done with a YAML file, e.g. ./configs/keycloak_bridge.yml. Default configurations are provided, that is if an entry is not present in the configuration file, it will be set to its default value.

The documentation for the Influx, Sentry, Jaeger and Debug configuration are common to all microservices and is provided in the Cloudtrust Gitbook.

The configurations specific to the keycloak-bridge are described in the next sections.

Component

For the component, the following parameters are available:

Key	Description	Default value
internal-http-host-port	HTTP server listening address	0.0.0.0:8888
management-http-host-port	HTTP server listening address	0.0.0.0:8877
account-http-host-port	HTTP server listening address	0.0.0.0:8866
register-http-host-port	HTTP server listening address	0.0.0.0:8855

Keycloak

Key	Description	Default value
keycloak-api-uri	Keycloak protocol:host:port	"http://127.0.0.1:8080"
keycloak-oidc-uri	Keycloak protocol:host:port (multiple value supported)	"http://127.0.0.1:8080 http://localhost:8080"
keycloak-timeout	Keycloak requests timeout in milliseconds	5000

Health check

Key	Description	Default value
livenessprobe-cache-duration	Health check results are not re-evaluated under this number of milliseconds	500
livenessprobe-http-timeout	Timeout in milliseconds for HTTP checks	900

ENV variables

Some parameters can be overridden with following ENV variables:

ENV Variable	Parameter
CT_BRIDGE_REGISTER_USERNAME	register-techuser-username
CT_BRIDGE_REGISTER_PASSWORD	register-techuser-password
CT_BRIDGE_REGISTER_CLIENT_ID	register-techuser-client-id
CT_BRIDGE_RECAPTCHA_SECRET	recaptcha-secret
CT_BRIDGE_DB_AUDIT_RW_USERNAME	db-audit-rw-username
CT_BRIDGE_DB_AUDIT_RW_PASSWORD	db-audit-rw-password
CT_BRIDGE_DB_AUDIT_RO_USERNAME	db-audit-ro-username
CT_BRIDGE_DB_AUDIT_RO_PASSWORD	db-audit-ro-password
CT_BRIDGE_DB_CONFIG_USERNAME	db-config-username
CT_BRIDGE_DB_CONFIG_PASSWORD	db-config-password
CT_BRIDGE_DB_USERS_USERNAME	db-users-username
CT_BRIDGE_DB_USERS_PASSWORD	db-users-password
CT_BRIDGE_INFLUX_USERNAME	influx-username
CT_BRIDGE_INFLUX_PASSWORD	influx-password
CT_BRIDGE_SENTRY_DSN	sentry-dsn
CT_BRIDGE_EVENT_BASIC_AUTH	event-basic-auth-token

Usage

Launch the keycloak bridge:

./bin/keycloak_bridge --config-file <path/to/config/file.yml> --authorization-file <path/to/config/file.json>

It is recommended to always provides an absolute path to the configuration file when the service is started, even though absolute and relative paths are supported. If no configuration file is passed, the service will try to load the default config file at ./configs/keycloak_bridge.yml, and if it fails it launches the service with the default parameters.

It is manadatory to load an authorization JSON file, if no authorization file is passed, the service will try to load the default file at ./configs/authorization.json, and if it fails the bridge refuse to start.

Keycloak events

The keycloak event-emitter module sends all events to the bridge's event endpoint. The event emitter use HTTP with flatbuffers.

Monitoring of keycloak-bridge

An endpoint allows to get a status of the Bridge and its components health. URL: http://{bridge.host}:{bridge.port}/health/check

Status example:

{
 "name": "keycloak-bridge",
 "state": "DOWN",
 "details": [
  {
   "name": "Audit R/W",
   "type": "database",
   "state": "DOWN",
   "message": "bad connection"
  },
  {
   "name": "Config RO",
   "type": "database",
   "state": "UP",
   "connection": "established"
  },
  {
   "name": "Keycloak",
   "type": "http",
   "state": "DOWN",
   "message": "Can't hit target: Get http://127.0.0.1:8080: dial tcp 127.0.0.1:8080: connectex: No connection could be made because the target machine actively refused it."
  }
 ]
}

About monitoring

Each HTTP request will trigger a set of operations that are going to be logged, measured, tracked and traced. For those information to be usable, we must be able to link the logs, metrics, traces and error report together. We achieve that with a unique correlation ID. For a given request, the same correlation ID will appear on the logs, metrics, traces and error report.

Note: InfluxDB indexes tags, so we put the correlation ID as tags to speed up queries. To query a tag, do not forget to simple quote it, otherwise it always returns empty results.

select * from "<measurement>" where "correlation_id" = '<correlation_id>';

Note: In Jaeger UI, to search traces with a given correlation ID you must copy the following in the "Tags" box:

correlation_id:<correlation_id>

Tests

Gomock is used to automatically generate mocks. See the Cloudtrust Gitbook for more information.

The unit tests don't cover:

• keycloak_bridge (./cmd/keycloak_bridge.go)

The first two are provided as example.

The keycloak_bridge.go is mostly just the main function doing all the wiring, it is difficult to test it with unit tests. It is covered by our integration tests.

Documentation

Overview

Keycloak bridge is a service dedicated to keycloak interactions.