feat: remove username field from registration, fix invalid credentials message#117
Open
feat: remove username field from registration, fix invalid credentials message#117
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
…s message
📄 Pull Request Description
🧩 What was changed?
Removed the username field from the Keycloak registration form. Updated the invalid credentials error message to use "email" instead of "username" in both English and Polish.
💡 Why was it changed?
The app uses email as username (registrationEmailAsUsername = true in Keycloak), so the username field was redundant and confusing for users. The error message "Invalid username or password" was also misleading since users log in with email.
⚙️ How was it implemented?
Removed the username input field from RegisterPage component in KcPage.tsx
Added custom translation override for invalidUserMessage key in i18n.ts for both EN and PL
None
✅ Checklist