6
Make Apple provider Secret Key optional for native-only Sign in with Apple
Source: supabase/supabase#44217 · opened by @fittar
When using native iOS Sign in with Apple (via React Native Expo), the Secret Key is not used. The OS handles authentication and provides an id_token directly to Supabase. The Secret Key is only needed for web-based OAuth flows. However, the Apple provider settings page in the Supabase Dashboard requires a Secret Key to save any changes. This means that if you need to add a new bundle ID to the Client IDs field (e.g. when adding a new white-label app), you cannot save without also providing a Secret Key, even if you don't need one. Expected behavior: The Secret Key field should be optional, or the UI should clearly indicate it's only required for web-based OAuth. Developers using native-only Apple Sign In should be able to update Client IDs without being blocked. Context: We run multiple white-label apps (each with their own bundle ID) using native iOS Sign in with Apple. When adding a new app's bundle ID to the Client IDs list, we were blocked from saving becau…
No pledges yet. Be the first to back this.
Comments
Similar requests
Add Support for Optional Descriptions for Secrets
1 vote · 0 comments
Move Away from Using Environment Variables for Secrets
1 vote · 0 comments
Ability to use any third party auth with asymmetric key
5 votes · 0 comments
Upload non-secret environment variables to Edge Function Secrets Management
4 votes · 0 comments
Adding custom API keys with selectable Postgres role for backend components
1 vote · 0 comments
No comments yet.