Describe the bug
Hi!

When I was testing and setting up SSE-KMS, I first setup using an application role. Upon saving the configuration, it said application role was not supported at this time and use a token instead.

I configured it to use a token. If I refresh the status it rotates between "KMS is running and healthy" and "Failed to create KMS backend: Backend error: AppRole authentication not yet implemented. Please use token authentication."

It's like there is somehow some residual configuration? I dont know how to delete and start over with KMS configuration. Trying to create the key results in the "failed to save key".

Ubuntu 24.04 latest
3 node setup
nginx reverse proxy
rustfs 1.0.0-alpha.67
Hashicorp Vault 1.20.1

To Reproduce
Steps to reproduce the behavior:
These steps assume you have access to a working Hashicorp Vault Instance with proper permissions etc.

1. Setup KMS configuration to use app role
2. Save configuration (get error about not supported)
3. Edit Configuration again and switch to a token. Provide valid token
4. Save configuration again.
5. Status saying running and healthy.
6. Refresh "KMS Status Overview"
7. It says ERROR and it trying to use the previous configuration

Expected behavior
I would expect being able to modify the SSE-KMS configuration (switch from app role to token) to save and persist... across refreshes/browser reloads. Or some way to delete and recreate?

Screenshots

Desktop (please complete the following information):

• MacOS 26.1
• Mozilla 144.0.2