Re-enrol deleted entity

[fooflington]

After deleting an entity (using /api/v1/admin/subordinates/{subordinateID}) it does not appear to be possible to use the /enroll_request endpoint for the same entity.

Called DELETE /api/v1/admin/subordinates/{subordinateID} which returned 204 as expected. Subsequent calls return 404.

Checking the database, deleted_at is populated:

             id = 1
     created_at = 1784649805
     updated_at = 1784891600
     deleted_at = 2026-07-24 11:11:29.915932722+00:00
      entity_id = https://rp.example.com
    description =
         status = 2
        jwks_id = 5
       metadata =
metadata_policy =
    constraints =

A GET for /api/v1/admin/subordinates or /api/v1/admin/subordinates/{subordinateID} both return 404.

Making a call to /enroll_request?sub=... returns 202 but lhcli says there's No pending requests:

# /lhcli subordinates requests -p
2026/07/24 11:23:24 Loaded Config
INFO[0000] Loaded storage backend
No pending requests

Calling PUT /api/v1/admin/subordinates/{subordinateID}/status with active returned a 404.

Without editing the database, is there a way to recover a deleted entity subordinate?

[zachmann]

There should be. Soft-delete can cause this undesired behavior. We have already fixed this on other endpoints (I remember the admin api subordinate management endpoint), but I might have missed this on the enroll request endpoint. I'll investigate.

[zachmann]

Should be fixed in the newest version on :main in a few minutes.