You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a copy of a troubleshooting article on Supabase's docs site. It may be missing some details from the original. View the original article.
If you can still decrypt existing Vault secrets after an attempted key rotation, the project is still using the legacy root key. The Supabase Management API /pgsodium endpoint is the correct mechanism for key rotation, but it requires a specific format to trigger the update across the database instance.
How to rotate the root key
Generate a new 64-character hexadecimal string to serve as the root key.
Issue a PUT request to the project's /pgsodium Management API endpoint using a valid Personal Access Token.
Pass the new 64-character hex key in the request body.
Verify rotation by attempting to decrypt data encrypted with the previous key. After rotation, you can no longer decrypt legacy data.
Manually re-encrypt or re-store your Vault secrets using the new key configuration.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
This is a copy of a troubleshooting article on Supabase's docs site. It may be missing some details from the original. View the original article.
If you can still decrypt existing Vault secrets after an attempted key rotation, the project is still using the legacy root key. The Supabase Management API
/pgsodiumendpoint is the correct mechanism for key rotation, but it requires a specific format to trigger the update across the database instance.How to rotate the root key
/pgsodiumManagement API endpoint using a valid Personal Access Token.All reactions