mirror of
https://github.com/supabase/supabase.git
synced 2026-05-06 17:00:27 -04:00
Chris Chinchilla
765aac4f2f
* Finesse toggles * Prettier * fix --------- Co-authored-by: Charis Lam <26616127+charislam@users.noreply.github.com>
46 lines
2.5 KiB
Plaintext
46 lines
2.5 KiB
Plaintext
---
|
|
id: 'auth'
|
|
title: 'Auth'
|
|
description: 'Use Supabase to Authenticate and Authorize your users.'
|
|
subtitle: 'Use Supabase to authenticate and authorize your users.'
|
|
tocVideo: '6ow_jW4epf8'
|
|
---
|
|
|
|
Supabase Auth makes it easy to implement authentication and authorization in your app. We provide client SDKs and API endpoints to help you create and manage users.
|
|
|
|
Your users can use many popular Auth methods, including password, magic link, one-time password (OTP), social login, and single sign-on (SSO).
|
|
|
|
## About authentication and authorization
|
|
|
|
Authentication and authorization are the core responsibilities of any Auth system.
|
|
|
|
- **Authentication** means checking that a user is who they say they are.
|
|
- **Authorization** means checking what resources a user is allowed to access.
|
|
|
|
Supabase Auth uses [JSON Web Tokens (JWTs)](/docs/guides/auth/jwts) for authentication. For a complete reference of all JWT fields, see the [JWT Fields Reference](/docs/guides/auth/jwt-fields). Auth integrates with Supabase's database features, making it easy to use [Row Level Security (RLS)](/docs/guides/database/postgres/row-level-security) for authorization.
|
|
|
|
## The Supabase ecosystem
|
|
|
|
You can use Supabase Auth as a standalone product, but it's also built to integrate with the Supabase ecosystem.
|
|
|
|
Auth uses your project's Postgres database under the hood, storing user data and other Auth information in a special schema. You can connect this data to your own tables using triggers and foreign key references.
|
|
|
|
Auth also enables access control to your database's automatically generated [REST API](/docs/guides/api). When using Supabase SDKs, your data requests are automatically sent with the user's Auth Token. The Auth Token scopes database access on a row-by-row level when used along with [RLS policies](/docs/guides/database/postgres/row-level-security).
|
|
|
|
<$Show if="authentication:show_providers">
|
|
<$Partial path="providers.mdx" />
|
|
</$Show>
|
|
|
|
<$Show if="billing:all">
|
|
|
|
## Pricing
|
|
|
|
Charges apply to Monthly Active Users (MAU), Monthly Active Third-Party Users (Third-Party MAU), and Monthly Active SSO Users (SSO MAU) and Advanced MFA Add-ons. For a detailed breakdown of how these charges are calculated, refer to the following pages:
|
|
|
|
- [Pricing MAU](/docs/guides/platform/manage-your-usage/monthly-active-users)
|
|
- [Pricing Third-Party MAU](/docs/guides/platform/manage-your-usage/monthly-active-users-third-party)
|
|
- [Pricing SSO MAU](/docs/guides/platform/manage-your-usage/monthly-active-users-sso)
|
|
- [Advanced MFA - Phone](/docs/guides/platform/manage-your-usage/advanced-mfa-phone)
|
|
|
|
</$Show>
|