DumbMonit
ИнтеграцииБезопасность и учётные записи
Мониторинг Keycloak в DumbMonit
БетаReadiness and database health, version, realms (disabled ones), active sessions and users per realm.
ДокументацияОфициальный сайт: Keycloak
Описания на английском, как в самом продукте. Подписи на странице — на вашем языке.
Что проверяет DumbMonit
Whether Keycloak can really log people in: readiness with the database check, version, realms (a disabled one is a locked-out population), and, with a service account, active sessions and users per realm.
Типичное применение. Identity: readiness and database, realms, sessions, users
Примеры
- Keycloak 25 and later
- Keycloak 24 and earlier
Как подключается
Что понадобится
- Client ID / secretA service-account client with read-only roles. DumbMonit asks for a token at each probe.
Учётная запись не нужна.
Сетевые порты, которые нужно открыть
8080/TCPAPI (HTTP, default)9000/TCPHealth checks on the management port (Keycloak 25 and later)443/TCPOnly with the https scheme behind a reverse proxy
Шаги настройки: Let DumbMonit read Keycloak's health and realms
Run Keycloak with health checks on, with the option below. From Keycloak 25 they answer on the management port 9000.
KC_HEALTH_ENABLED=trueOptional, for realms, sessions and users: in the master realm, create a client named as follows, with Client authentication and Service accounts roles on, and Standard flow off.
dumbmonitOn that client's Service accounts roles tab, assign the client roles listed below, then copy the secret from its Credentials tab.
In DumbMonit, enter Keycloak's address and the client ID and secret, or choose None (health checks only).
Обратите внимание. Keycloak 24 and earlier serve the health checks on the main port: set the health port option to same. Health checks must be enabled on the server, or DumbMonit reports a missing /health/ready.