Files
supabase/apps/studio/components/interfaces/Docs/Authentication.tsx
Gildas Garcia 43300d43ce chore: consolidate useAPIKeysQuery + getKeys into a single useAPIKeys hook (#46761)
## Problem

- API may return a non-array shape that can crash `getKeys` because of
an hard coded cast
- getting API keys is cumbersome as consumers have to call two functions

## Solution

- consolidate `useAPIKeysQuery` + `getKeys` into a single `useAPIKeys`
hook
- guard `getKeys` so that it doesn't crash if passed a non array value
- update usages

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

* **Refactor**
* Unified how project API keys are retrieved across the studio,
resulting in more consistent loading/error handling and slight
responsiveness improvements when showing keys and related command
snippets. UI and permissions behavior remain unchanged for end users.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
2026-06-09 15:49:10 +02:00

140 lines
4.9 KiB
TypeScript

import { PermissionAction } from '@supabase/shared-types/out/constants'
import { useParams } from 'common'
import CodeSnippet from './CodeSnippet'
import { DocSection } from './DocSection'
import Snippets from './Snippets'
import { InlineLink } from '@/components/ui/InlineLink'
import { useAPIKeys } from '@/data/api-keys/api-keys-query'
import { useProjectSettingsV2Query } from '@/data/config/project-settings-v2-query'
import { useAsyncCheckPermissions } from '@/hooks/misc/useCheckPermissions'
interface AuthenticationProps {
selectedLang: 'bash' | 'js'
showApiKey: string
}
const Authentication = ({ selectedLang, showApiKey }: AuthenticationProps) => {
const { ref: projectRef } = useParams()
const { can: canReadAPIKeys } = useAsyncCheckPermissions(PermissionAction.SECRETS_READ, '*')
const { data: apiKeyData } = useAPIKeys({ projectRef }, { enabled: canReadAPIKeys })
const { anonKey, serviceKey } = apiKeyData ?? {}
const { data: settings } = useProjectSettingsV2Query({ projectRef })
const protocol = settings?.app_config?.protocol ?? 'https'
const hostEndpoint = settings?.app_config?.endpoint
const endpoint = `${protocol}://${hostEndpoint ?? ''}`
// [Joshen] ShowApiKey should really be a boolean, its confusing
const defaultApiKey =
showApiKey !== 'SUPABASE_KEY'
? (anonKey?.api_key ?? 'SUPABASE_CLIENT_API_KEY')
: 'SUPABASE_CLIENT_API_KEY'
const serviceApiKey =
showApiKey !== 'SUPABASE_KEY'
? (serviceKey?.api_key ?? 'SUPABASE_SERVICE_KEY')
: 'SUPABASE_SERVICE_KEY'
return (
<div className="flex flex-col flex-1">
<DocSection
title="Authentication"
content={
<>
<p>Supabase works through a mixture of JWT and Key auth.</p>
<p>
If no <code>Authorization</code> header is included, the API will assume that you are
making a request with an anonymous user.
</p>
<p>
If an <code>Authorization</code> header is included, the API will "switch" to the role
of the user making the request. See the User Management section for more details.
</p>
<p>We recommend setting your keys as Environment Variables.</p>
</>
}
/>
<DocSection
title="Client API Keys"
content={
<>
<p>
Client keys allow "anonymous access" to your database, until the user has logged in.
After logging in the keys will switch to the user's own login token.
</p>
<p>
In this documentation, we will refer to the key using the name{' '}
<code>SUPABASE_KEY</code>.
</p>
<p>
We have provided you a Client Key to get started. You will soon be able to add as many
keys as you like. You can find the <code>anon</code> key in the{' '}
<InlineLink href={`/project/${projectRef}/settings/api-keys`}>
API Keys Settings
</InlineLink>{' '}
page.
</p>
</>
}
snippets={
<>
<CodeSnippet
selectedLang={selectedLang}
snippet={Snippets.authKey('CLIENT API KEY', 'SUPABASE_KEY', defaultApiKey)}
/>
<CodeSnippet
selectedLang={selectedLang}
snippet={Snippets.authKeyExample(defaultApiKey, endpoint, {
showBearer: false,
})}
/>
</>
}
/>
<DocSection
title="Service Keys"
content={
<>
<p>
Service keys have FULL access to your data, bypassing any security policies. Be VERY
careful where you expose these keys. They should only be used on a server and never on
a client or browser.
</p>
<p>
In this documentation, we will refer to the key using the name{' '}
<code>SERVICE_KEY</code>.
</p>
<p>
We have provided you with a Service Key to get started. Soon you will be able to add
as many keys as you like. You can find the <code>service_role</code> in the{' '}
<InlineLink href={`/project/${projectRef}/settings/api-keys`}>
API Keys Settings
</InlineLink>{' '}
page.
</p>
</>
}
snippets={
<>
<CodeSnippet
selectedLang={selectedLang}
snippet={Snippets.authKey('SERVICE KEY', 'SERVICE_KEY', serviceApiKey)}
/>
<CodeSnippet
selectedLang={selectedLang}
snippet={Snippets.authKeyExample(serviceApiKey, endpoint, {
keyName: 'SERVICE_KEY',
})}
/>
</>
}
/>
</div>
)
}
export default Authentication