Introduce a "Secret" object #24961

Activity

1. emilburzo

   added

   triageAdd this label to issues that need to be triagedAdd this label to issues that need to be triaged

   on Aug 10, 2026
2. dewi-tik

   added

   enhancement/confirmedEnhancements that will be implemented in the futureEnhancements that will be implemented in the future

   on Aug 10, 2026
3. github-project-automation

   added this to authentik Coreon Aug 10, 2026
4. github-project-automation

   moved this to Todo in authentik Coreon Aug 10, 2026
5. dewi-tik

   removed

   triageAdd this label to issues that need to be triagedAdd this label to issues that need to be triaged

   on Aug 13, 2026
6. dewi-tik

   added this to the Release 2026.11.0: Required milestone on Aug 13, 2026
7. dewi-tik

   added the

   Feature

   issue type on Aug 13, 2026
8. BeryJu commented on Aug 25, 2026

   

   BeryJu

   on Aug 25, 2026

   Member

   More actions

   Initial iteration: Secret Object with a blob, type, name field

   Usual rbac, different input fields depending on type (text/codemirror/file)
   Separate objects for each value
   In consuming objects, rename current field to _current_field and keep db_column, add new field as foreign key, in migration backfill, next release remove old field
   Also needs UX to be able to create secrets inline in forms
   keep internal API in a shape that potentially allows for multiple keys in a single secret

   Second iteration

   SecretSource, integration with Vault/etc to pull data; investigate rotation
9. dominic-r

   self-assigned this

   on Aug 30, 2026
10. dominic-r

    linked a pull request that will close this issuecrypto: add managed secrets API #25415on Aug 30, 2026