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
Minor update to new API keys modal for disabling / reenabling legacy keys (supabase#36554)
* Minor update to new API keys modal for disabling / reenabling legacy keys
* Minor update
* Refresh user count as well when clicking refresh in auth users management
description: `If you disable your anon and service_role keys while they are in use, your applications will stop functioning. All API endpoints will receive HTTP 401 Unauthorized. Make sure you are no longer using them before proceeding.`,
124
+
title: 'Ensure legacy keys are no longer in use before disabling',
125
+
description: (
126
+
<spanclassName="prose text-sm">
127
+
Disabling <code>anon</code> and <code>service_role</code> keys while they are in
128
+
use will cause downtime for your application. Ensure they are no longer in use
129
+
before proceeding.
130
+
</span>
131
+
),
121
132
}
122
133
: {
123
-
title: 'Prefer publishable and secret keys',
124
-
description:
125
-
'While re-enabling anon and service_role keys makes sense in some cases, a better and more secure alternative is the publishable or secret key. Consider using those before proceeding!',
134
+
title: 'Publishable and secret keys are preferred',
135
+
description: (
136
+
<spanclassName="prose text-sm">
137
+
Re-enabling <code>anon</code> and <code>service_role</code> keys may be
138
+
appropriate in certain cases, but using a publishable and secret key is more
139
+
secure. We recommend against re-enabling legacy API keys
0 commit comments