Rotate Authentik secrets exposed during ideahunter recon #2
Labels
No labels
bug
documentation
enhancement
infra
integration
priority:high
priority:low
priority:medium
research
security
tech-debt
ux
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
frank/App-Idea-Hunter#2
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What happened
During 2026-07-12 recon for the ideahunter.fmrdigital.dev deployment, a subagent ran
docker exec authentik-server envon fmrdigital (100.119.88.80) to inspect Authentik's provider config. This dumped plaintext secrets into that agent's own transcript. Nothing was transmitted externally, but per the mandatory secret-leak-prevention policy these count as exposed and should be rotated.Exposed values (rotate these)
AUTHENTIK_EMAIL__PASSWORD(Resend SMTP key)AUTHENTIK_BOOTSTRAP_TOKENAUTHENTIK_SECRET_KEYAUTHENTIK_POSTGRESQL__PASSWORDAUTHENTIK_BOOTSTRAP_PASSWORDOwner
User (Frank) opted to handle rotation personally rather than have it done as part of the ideahunter session � filed here so it doesn't get lost. This affects the shared Authentik instance used by all fmrdigital.dev apps, not just this project.
See also:
decisions/2026-07-12-ideahunter-auth-architecture.mdin this repo for full context.