-
Notifications
You must be signed in to change notification settings - Fork 480
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature to delete individual keys from trust bundle #5375
Comments
Another case (but a somewhat special case) would be if you decided to change your server config to use a lower TTL than you initially started with, then you're stuck with the keys already created. |
I believe this would be covered by the ongoing "Forced Rotation and Revocation" work that @MarcosDY has been working through. |
@keeganwitt just to clarify, you're talking about removing keys from the trust bundle from your own trust domain, not from a federated trust domain, correct? |
If it involves revoking a key within your own trust domain, this will be possible once force rotation becomes available.
|
👋 hey @keeganwitt, friendly ping on answers to the question above :) |
In our case, yes, nested not federated. But I'd think this would apply to federated setups too (but I'd have to read through the code a bit more on that).
I think this would work, yes. I'm not sure if you were going to delete it from the bundle during revocation or set a |
Yes, once it has been revoked, it will be removed from the bundle and not show up in the key set advertised by the OIDC discovery provider. |
There are cases where it might be useful to delete specific keys from the trust bundle. Some examples are
Currently, the only option offered is to delete the entire bundle.
The text was updated successfully, but these errors were encountered: