Skip to content

fix: assorted links #390

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
hazel-nut merged 1 commit into from
Apr 7, 2026
Merged

fix: assorted links #390

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion main/docs/deploy-monitor/pre-deployment-checks/production-check-required-fixes.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ For more information about your checks output, see [Run Production Checks](/docs
| Support Email should be configured | Ensures the [Support Email](https://manage.auth0.com/#/account) is configured in Tenant Settings. |
| Support URL is configured | Ensures the [Support URL](https://manage.auth0.com/#/account) is configured in Tenant Settings. |
| Tenant Environment Tag should be configured | Ensures the [tenant environment tag](https://support.auth0.com/tenants/public) is set appropriately to Production, Staging, or Development. Changes to this tag affect your tenant's rate limit. |
| Tenant is set to use a recommended default [NodeJS version](/docs/troubleshoot/product-lifecycle/deprecations-and-migrations/migrate-actions-nodejs-16-to-nodejs-18ions-nodejs-16-to-nodejs-18) | Update your tenant to a [recommended version of NodeJS](/docs/troubleshoot/product-lifecycle/past-migrations/migrate-nodejs-16-to-nodejs-18) to take advantage of security patches and new features. |
| Tenant is set to use a recommended default [NodeJS version](/docs/troubleshoot/product-lifecycle/deprecations-and-migrations/migrate-nodejs-22) | Update your tenant to a [recommended version of NodeJS](/docs/troubleshoot/product-lifecycle/past-migrations/migrate-nodejs-16-to-nodejs-18) to take advantage of security patches and new features. |
| Tenant Login URI | Ensures that [Tenant Login URI](https://manage.auth0.com/#/tenant/advanced) is configured in Tenant Settings. |
| Use Custom Domain in Branded Email Templates | Ensure your emails templates use a [custom domain](/docs/customize/custom-domains/configure-features-to-use-custom-domains#use-custom-domains-in-emails). We strongly recommend customizing all user-facing emails to use your custom domain and company branding. |

Expand Down
2 changes: 1 addition & 1 deletion ...docs/get-started/architecture-scenarios/business-to-business/authentication.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -149,7 +149,7 @@ Once you've figured out how you want to authenticate your users, the next step i

<Warning>

Native mobile applications (and desktop applications) should use the system browser for authentication, or they open themselves up to additional security risks. See [Native vs. Browser Login on Mobile](/docs/get-started/authentication-and-authorization-flow/device-authorization-flow/mobile-device-login-flow-best-practices) for more information.
Native mobile applications (and desktop applications) should use the system browser for authentication, or they open themselves up to additional security risks. See [Native Login](/docs/authenticate/login/native-login) for more information.

</Warning>

Expand Down
2 changes: 1 addition & 1 deletion ...docs/get-started/architecture-scenarios/business-to-consumer/authentication.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,7 +72,7 @@ Once you've figured out how you want to authenticate your users, the next step i

<Warning>

Native mobile applications (and desktop applications) should use the system browser for authentication, or they open themselves up to additional security risks. See [Native vs. Browser Login on Mobile](/docs/get-started/authentication-and-authorization-flow/device-authorization-flow/mobile-device-login-flow-best-practices) for more information.
Native mobile applications (and desktop applications) should use the system browser for authentication, or they open themselves up to additional security risks. See [Native Login](/docs/authenticate/login/native-login) for more information.

</Warning>

Expand Down
4 changes: 2 additions & 2 deletions main/docs/quickstart/native/xamarin.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ import {AuthCodeBlock} from "/snippets/AuthCodeBlock.jsx";

# .NET Android and iOS

<Frame>![Gravatar for frederik.prijck@auth0.com](/docs/www.gravatar.com/avatar/b74fc62fbaf2a93d1db3c549f62d4d9a?d=mm&r=g&s=50)</Frame>
<Frame>![Gravatar for frederik.prijck@auth0.com](https://www.gravatar.com/avatar/b74fc62fbaf2a93d1db3c549f62d4d9a?d=mm&r=g&s=50)</Frame>

##### By Frederik Prijck

Expand Down Expand Up @@ -353,4 +353,4 @@ BrowserResultType browserResult = await client.LogoutAsync();



[Edit on GitHub](https://github.com/auth0/docs/edit/master/articles/quickstart/native/net-android-ios/01-login.md)
[Edit on GitHub](https://github.com/auth0/docs/edit/master/articles/quickstart/native/net-android-ios/01-login.md)
2 changes: 1 addition & 1 deletion main/docs/quickstart/webapp/golang/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -533,7 +533,7 @@ func Handler(ctx *gin.Context) {


<Info>
The redirect URL needs to be in the list of Allowed Logout URLs in the settings section of the application, For more information, see [Redirect Users After Logout](/docs/authenticate/login/logout/guides/redirect-users-after-logout).
The redirect URL needs to be in the list of Allowed Logout URLs in the settings section of the application, For more information, see [Redirect Users After Logout](/docs/authenticate/login/logout/redirect-users-after-logout).
</Info>

Create a file called `user.js` in the folder `web/static/js`, and add the code to remove the cookie from a logged-in
Expand Down
Loading