forked from nhost/nhost
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Sync Fork
committed
Feb 17, 2024
1 parent
0f77c94
commit 622f87a
Showing
38 changed files
with
430 additions
and
41 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,111 @@ | ||
--- | ||
title: Overview | ||
description: Learn about Nhost Auth | ||
icon: hand-wave | ||
--- | ||
|
||
Nhost Auth is a ready-to-use authentication service seamlessly integrated with the [GraphQL API](/product/graphql) and its [Permission System](/guides/api/permissions) from Hasura. This allows you to easily add user authentication to your application without having to build and maintain your own authentication system. | ||
|
||
## Supported Methods | ||
|
||
<CardGroup cols={4}> | ||
<Card title="Email and Password" icon="square-1" href="/guides/auth/sign-in-email-password"> | ||
</Card> | ||
<Card title="Magic Link" icon="square-2" href="/guides/auth/sign-in-magic-link"> | ||
</Card> | ||
<Card title="Phone Number (SMS)" icon="square-3" href="/guides/auth/sign-in-phone-number"> | ||
</Card> | ||
<Card title="Security Keys (WebAuthn)" icon="square-4" href="/guides/auth/sign-in-webauthn"> | ||
</Card> | ||
<Card title="Elevated Permissions" icon="square-5" href="/guides/auth/elevated-permissions"> | ||
</Card> | ||
</CardGroup> | ||
|
||
### OAuth Providers | ||
|
||
<CardGroup cols={4}> | ||
<Card title="Apple" icon="square-1" href="/guides/auth/social/sign-in-apple"> | ||
</Card> | ||
<Card title="Discord" icon="square-2" href="/guides/auth/social/sign-in-discord"> | ||
</Card> | ||
<Card title="Facebook" icon="square-3" href="/guides/auth/social/sign-in-facebook"> | ||
</Card> | ||
<Card title="GitHub" icon="square-4" href="/guides/auth/social/sign-in-github"> | ||
</Card> | ||
<Card title="Google" icon="square-5" href="/guides/auth/social/sign-in-google"> | ||
</Card> | ||
<Card title="Linkedin" icon="square-6" href="/guides/auth/social/sign-in-linkedin"> | ||
</Card> | ||
<Card title="Spotify" icon="square-7" href="/guides/auth/social/sign-in-spotify"> | ||
</Card> | ||
<Card title="Twitch" icon="square-8" href="/guides/auth/social/sign-in-twitch"> | ||
</Card> | ||
<Card title="WorkOS" icon="square-9" href="/guides/auth/social/sign-in-workos"> | ||
</Card> | ||
</CardGroup> | ||
|
||
## Client URL | ||
|
||
Client URL is the URL of your frontend application. The Client URL is used to redirect the user in certain auth workflows like signing in or resetting a password. | ||
|
||
## Allowed Redirect URLs | ||
|
||
Allowed Redirect URLs are the URLs of your frontend application that users are allowed to be redirected to on specific auth workflows. This is useful if you have multiple applications using the same Nhost backend or if you want to redirect users to a specific URL after certain authentication workflows. | ||
|
||
As an example, for a staging project, you can set the Client URL to `https://staging.example.com` and Allowed Redirect URLs to `https://*.vercel.app`. This way, the user can be redirected to any Vercel deployment of your frontend application. | ||
|
||
## Allowed Emails and Domains | ||
|
||
Allowed Emails and Domains are used to restrict what email adresses and domains are valid when signing up and signing in. | ||
|
||
If both allowed emails and allowed domains are set a user can only sign up if their email address matches one of the allowed emails or one of the allowed domains. | ||
|
||
## Blocked Emails and Domains | ||
|
||
Blocked Emails and Domains are used to block specific email addresses and domains from signing up and signing in. | ||
|
||
Note that even if a user's email address matches any allowed email or domain, they will still be blocked if their email address matches any blocked email or domain. | ||
|
||
## Multi-factor Authentication | ||
|
||
By enabling Multi-Factor Authentication (MFA), you can allow users to verify their identity using a second factor during the sign-in process. We currently support Authenticator Apps (TOTP) for MFA. | ||
|
||
A user can enable MFA for their account by scanning a QR code with their Authenticator App. After that, they will be prompted to enter a code generated by their Authenticator App during the sign-in process. | ||
|
||
## Gravatar | ||
|
||
If Gravatar is enabled, Nhost Auth will use the user's email address to fetch their Gravatar profile picture. If the user doesn't have a Gravatar profile picture, a default image will be used. | ||
|
||
There are two options for Gravatars. | ||
|
||
<Steps> | ||
<Step title="Default Image"> | ||
|
||
If the user doesn't have a Gravatar profile picture, a default image will be used. You can choose between the following options: | ||
|
||
- `404`: Do not load any image if none is associated with the email hash, instead return an HTTP 404 (File Not Found) response. | ||
- `mp`: (mystery-person) a simple, cartoon-style silhouetted outline of a person (does not vary by email hash). | ||
- `identicon`: a geometric pattern based on an email hash. | ||
- `monsterid`: a generated 'monster' with different colors, faces, etc. | ||
- `wavatar`: generated faces with differing features and backgrounds. | ||
- `retro`: awesome generated, 8-bit arcade-style pixelated faces. | ||
- `robohash`: a generated robot with different colors, faces, etc. | ||
- `blank`: a transparent PNG image. | ||
|
||
</Step> | ||
|
||
<Step title="Rating"> | ||
|
||
Gravatar images are rated by default. You can choose between the following options: | ||
|
||
- `g`: suitable for display on all websites with any audience type. | ||
- `pg`: may contain rude gestures, provocatively dressed individuals, lesser swear words or mild violence. | ||
- `r`: may contain such things as harsh profanity, intense violence, nudity, or hard drug use. | ||
- `x`: may contain hardcore sexual imagery or extremely disturbing violence. | ||
|
||
</Step> | ||
</Steps> | ||
|
||
## Disable New Users | ||
|
||
If set, newly registered users are disabled and won't be able to sign in. This is useful if you want to manually approve new users before they can sign in. |
Oops, something went wrong.