DumbMonit
IntégrationsSécurité et identité
Surveiller Keycloak avec DumbMonit
BêtaReadiness and database health, version, realms (disabled ones), active sessions and users per realm.
DocumentationSite officiel : Keycloak
Les descriptions des produits sont en anglais, comme dans le produit. Les libellés de la page suivent votre langue.
Ce que DumbMonit surveille
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.
Usage typique. Identity: readiness and database, realms, sessions, users
Exemples
- Keycloak 25 and later
- Keycloak 24 and earlier
Comment il se connecte
Ce qu'il faut
- Client ID / secretA service-account client with read-only roles. DumbMonit asks for a token at each probe.
Aucun compte nécessaire.
Ports réseau à ouvrir
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
Étapes de mise en place: 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).
À savoir. 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.