Prevent authenticated users from accessing login and signup pages #659
Conversation
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
|
tjementum
deleted the
pp-252-prevent-already-logged-in-users-from-logging-in-or-signing
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary & Motivation
Prevent already logged in users from logging in or signing up for a new tenant. The
useIsAuthenticatedhook has been fixed to correctly check the authentication state, ensuring accurate redirects. Authenticated users attempting to access anonymous pages like the landing page, login, or signup are now redirected to the admin center.Additionally, unused authentication-related components, constants, and hooks have been removed to clean up the codebase.
Checklist