mirror of
https://github.com/supabase/supabase.git
synced 2026-10-06 18:05:11 +03:00
Pamela Chia
5a7c0d6d84
I made the crawler renderer resolve legacy JavaScript and Dart reference slugs to their current sections, and updated authored guide and SDK spec links to use them. Exact slugs still win, ambiguous bare slugs still return 404, and `file-buckets-listv2` remains a section slug in canonical links. I kept the www redirect work in a separate draft PR because the apps deploy independently. ## To test - [x] On the Docs preview, request `reference/javascript/order` and `reference/dart/get-user` with a bot user agent. Expect the intended heading and canonical URL. - [x] Request `reference/javascript/file-buckets-listv2` with bot and browser user agents. Expect it to open the list v2 section. - [x] Request `reference/swift/get-user` and the Kotlin reference root with a bot user agent. Expect the intended heading. - [x] Open the Storage quickstart guide and follow its upload reference link. Expect the current JavaScript upload section. ## Linear refs GROWTH-1293 <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Bug Fixes** * Reference pages now resolve legacy aliases and ambiguous slugs more accurately, with canonical links that preserve explicit SDK versions. * SDK version paths are recognized only when the full path segment matches the version format, improving reference-page routing. * **Documentation** * Updated API reference links across authentication, storage, security, and SDK guides to point to current pages. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
39 lines
2.0 KiB
Plaintext
39 lines
2.0 KiB
Plaintext
---
|
|
id: 'product-security'
|
|
title: 'Secure configuration of Supabase products'
|
|
description: 'Supabase provides a secure yet flexible set of products. Here is how to adjust various security settings across the various products.'
|
|
---
|
|
|
|
The Supabase [production checklist](/docs/guides/deployment/going-into-prod) provides detailed advice on preparing an app for production. While our [SOC 2](/docs/guides/security/soc-2-compliance) and [HIPAA](/docs/guides/security/hipaa-compliance) compliance documents outline the roles and responsibilities for building a secure and compliant app.
|
|
|
|
Various products at Supabase have their own hardening and configuration guides, below is a definitive list of these to help guide your way.
|
|
|
|
## Auth
|
|
|
|
- [Password security](/docs/guides/auth/password-security)
|
|
- [Rate limits](/docs/guides/auth/rate-limits)
|
|
- [Bot detection / Prevention](/docs/guides/auth/auth-captcha)
|
|
- [JWTs](/docs/guides/auth/jwts)
|
|
|
|
## Database
|
|
|
|
- [Row Level Security](/docs/guides/database/postgres/row-level-security)
|
|
- [Column Level Security](/docs/guides/database/postgres/column-level-security)
|
|
- [Securing your API](/docs/guides/api/securing-your-api)
|
|
- [Custom claims and role based access control](/docs/guides/api/custom-claims-and-role-based-access-control-rbac)
|
|
- [Managing Postgres roles](/docs/guides/database/postgres/roles)
|
|
- [Managing secrets with Vault](/docs/guides/database/vault)
|
|
- [Postgres connection logging](/docs/guides/platform/postgres-connection-logging)
|
|
- [Superuser access and unsupported operations](/docs/guides/database/postgres/roles-superuser)
|
|
|
|
## Storage
|
|
|
|
- [Object ownership](/docs/guides/storage/security/ownership)
|
|
- [Access control](/docs/guides/storage/security/access-control)
|
|
- The Storage API docs contain hints about required [RLS policy permissions](/docs/reference/javascript/file-buckets-createbucket)
|
|
- [Custom roles with the storage schema](/docs/guides/storage/schema/custom-roles)
|
|
|
|
## Realtime
|
|
|
|
- [Authorization](/docs/guides/realtime/authorization)
|