#
The `` component is a crucial part of implementing custom OAuth flows in your application. It serves as the callback handler for the authentication process initiated by the `authenticateWithRedirect()` method. Render it on the route specified as the `redirectUrl` in your `authenticateWithRedirect()` call.
This component automatically handles the OAuth callback, completing the authentication process and managing the user's session. It uses the [handleRedirectCallback()](https://clerk.com/docs/astro/reference/objects/clerk.md#handle-redirect-callback) method under the hood.
## Example
For an example of how to use the `` component, see the [custom flow](https://clerk.com/docs/guides/development/custom-flows/authentication/oauth-connections.md?sdk=astro) guide.
## Properties
All props are optional.
| Name | Type | Description |
| -------------------------- | --------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| continueSignUpUrl? | string | undefined | null | The full URL or path to navigate to if the sign up requires additional information. |
| signInUrl? | string | The full URL or path where the component is mounted. |
| signUpUrl? | string | The full URL or path where the component is mounted. |
| signInFallbackRedirectUrl? | string | The fallback URL to redirect to after the user signs in, if there's no redirect\_url in the path already. Defaults to /. It's recommended to use the environment variable instead. |
| signUpFallbackRedirectUrl? | string | The fallback URL to redirect to after the user signs up, if there's no redirect\_url in the path already. Defaults to /. It's recommended to use the environment variable instead. |
| signInForceRedirectUrl? | string | If provided, this URL will always be redirected to after the user signs in. It's recommended to use the environment variable instead. |
| signUpForceRedirectUrl? | string | If provided, this URL will always be redirected to after the user signs up. It's recommended to use the environment variable instead. |
| firstFactorUrl? | string | undefined | The full URL or path to navigate to during sign in, if first factor verificationFirst factor is the first factor of authentication that is required to complete the authentication process. For example, when a user signs in with email and password, the password is the first factor. First factor verification is the process of verifying a user's identity using a single factor. This can be compared to second factor verificationSecond factor verification, also known as two-factor authentication (2FA) or multi-factor authentication (MFA), is the process of verifying a user's identity using an additional factor. For example, if a user signs in with their email and password, and then, is asked to also provide an OTPA one-time password (OTP) is a code that is used to authenticate a user. The OTP is typically sent to a user's email address or phone number and must be entered within a certain time period to be valid. sent to their phone number, the OTP is the second factorA second factor is an additional factor of authentication that is required to complete the authentication process. For example, if a user signs in with their email and password, and then is asked to also provide an OTPA one-time password (OTP) is a code that is used to authenticate a user. The OTP is typically sent to a user's email address or phone number and must be entered within a certain time period to be valid. sent to their email in order to verify their identity, the email OTP is the second factor.., also known as two-factor authentication (2FA) or multi-factor authentication (MFA), where the user needs to provide an additional factor to verify their identity. is required. |
| secondFactorUrl? | string | undefined | The full URL or path to navigate to during sign in, if multi-factor authentication is enabled. |
| resetPasswordUrl? | string | The full URL or path to navigate to during sign in, if the user is required to reset their password. |
| transferable? | boolean | A boolean that indicates whether or not sign in attempts are transferable to the sign up flow. Defaults to true. When set to false, prevents opaque sign upsAn opaque sign up refers to a specific OAuth authentication flow where a user attempts to sign in via OAuth (like Google, GitHub, etc.) with an email address that doesn't exist in your application's user database. The term "opaque" here means that the sign-up process is transparent to the user - they think they're signing in, but Clerk is actually creating a new account behind the scenesA transfer flow allows a user to both sign in and sign up in the same process. If a user tries signing up, but already exists, the flow will transfer the user to the sign-in flow. If a user tries signing in, but doesn't exist, the flow will transfer the user to the sign-up flow\.. when a user attempts to sign in via OAuth with an email that doesn't exist. |
| verifyEmailAddressUrl? | string | undefined | null | The full URL or path to navigate to after requesting email verification. |
| verifyPhoneNumberUrl? | string | undefined | null | The full URL or path to navigate to after requesting phone verification. |
---
## Sitemap
[Overview of all docs pages](https://clerk.com/docs/llms.txt)