Files
supabase/apps/studio/components/interfaces/Docs/Authentication.tsx
T
Charis f7bf7d7ce4 feat(studio): move data api docs to integrations section (#42749)
Feature / Refactor

## What is the current behavior?

Data API docs live at the `/api` route as a standalone page. Old links
point to the previous location.

## What is the new behavior?

Data API docs are moved to the integrations section with a dedicated
docs tab and settings tab. Old links are cleaned up, a mobile menu is
added for data API docs navigation, and minor code review fixes are
applied.

## Additional context

Resolves FE-2517

## Summary by CodeRabbit

* **New Features**
* Revamped API docs UI with reusable section layout, language toggle
(JS/Bash), API key selection, and improved code snippets
* Added Data API docs tab, mobile navigation, and dedicated
loading/error/disabled states

* **Navigation Updates**
* Moved API docs and related links into the Integrations/Data API area
and added redirects to new routes
* Updated various internal links to the new Data API settings and
overview locations

* **Tests**
  * Added comprehensive unit tests for Data API utilities
2026-02-12 15:57:44 -05:00

139 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 { getKeys, useAPIKeysQuery } 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: apiKeys } = useAPIKeysQuery({ projectRef }, { enabled: canReadAPIKeys })
const { data: settings } = useProjectSettingsV2Query({ projectRef })
const { anonKey, serviceKey } = getKeys(apiKeys)
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