DumbMonit
IntegracionesSeguridad e identidad
Monitorizar authentik con DumbMonit
BetaReadiness, workers, failed system tasks, outpost connections, version updates, users.
DocumentaciónSitio web oficial: authentik
Las descripciones están en inglés, como en el producto. Las etiquetas de la página siguen su idioma.
Qué vigila DumbMonit
Whether authentik can still sign people in and keep its background work running: readiness, workers, failed system tasks, outposts that stopped reporting, version updates and the number of users.
Uso habitual. Identity: readiness, workers, failed tasks, outposts, updates
Ejemplos
- authentik 2025.x
Cómo se conecta
Qué necesita
- API tokenThe key of an API token created for a service account, sent as "Authorization: Bearer …".
Puertos de red que abrir
9000/TCPAPI (HTTP, default)9443/TCPOnly with the https scheme on authentik's own HTTPS port443/TCPOnly with the https scheme behind a reverse proxy
Pasos de configuración: Create an API token in authentik
In authentik, open Directory → Users → Create a service account and name it as follows, without a random password.
dumbmonitPut that user in a group that can open the authentik interface, so it can read the system pages.
Open Directory → Tokens and App passwords, create a token for that user with the intent API Token and no expiry, and copy its key.
In DumbMonit, enter authentik's address and paste the key.
Ojo. authentik has no read-only role for its system pages: the token's user must be allowed into the interface, so keep the key only in DumbMonit. Pages the token cannot read are skipped, not failed.