github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-22 22:32:01 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

NextJS Sign-Up form on demo does not validate matching 'Password' and 'Confirm Password' fields #678

New Issue
Closed
opened 2026-03-13 07:59:59 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-03-13 07:59:59 -05:00
Owner
Copy Link

Originally created by @Rohan-Nair on GitHub (Feb 15, 2025).

Is this suited for github?

  • Yes, this is suited for github

To Reproduce

  1. Run the demo.
  2. Enter two different entries for the password and try to sign up.

Current vs. Expected behavior

Current Behaviour: Does not check if the password and confirm password fields are the same and sign's up the user even if the passwords do not match.

Expected Behaviour: An error toast should be displayed prompting the user to match the password and confirm password fields in the sign-up form.

What version of Better Auth are you using?

1.1.17

Provide environment information

- OS: Checked on Fedora 40 & Windows 11.
- Browser: Brave.

Which area(s) are affected? (Select all that apply)

Documentation, Client

Auth config (if applicable)

import { betterAuth } from "better-auth"
export const auth = betterAuth({
  emailAndPassword: {  
    enabled: true
  },
});

Additional context

No response

Originally created by @Rohan-Nair on GitHub (Feb 15, 2025). ### Is this suited for github? - [x] Yes, this is suited for github ### To Reproduce 1. Run the [demo](https://demo.better-auth.com/sign-in). 2. Enter two different entries for the password and try to sign up. ### Current vs. Expected behavior Current Behaviour: Does not check if the password and confirm password fields are the same and sign's up the user even if the passwords do not match. Expected Behaviour: An error toast should be displayed prompting the user to match the password and confirm password fields in the sign-up form. ### What version of Better Auth are you using? 1.1.17 ### Provide environment information ```bash - OS: Checked on Fedora 40 & Windows 11. - Browser: Brave. ``` ### Which area(s) are affected? (Select all that apply) Documentation, Client ### Auth config (if applicable) ```typescript import { betterAuth } from "better-auth" export const auth = betterAuth({ emailAndPassword: { enabled: true }, }); ``` ### Additional context _No response_
GiteaMirror added the bug label 2026-03-13 07:59:59 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
adapter
astro
awaiting external contributor
blocked
breaking
breaking change
bug
c-devops
core
credentials
database
dependencies
devops
devtools
docs
documentation
duplicate
elysia
enhancement
enterprise
expo
express
fastify
good first issue
help wanted
hono
identity
infra
integration
invalid
javascript
locked
maintenance
need-more-information
needs: info
needs: repro
nextjs
nuxt
oauth
organization
P0
payments
perf
platform
plugin
pull-request
Mirrored from GitHub Pull Request
 question
ready
regression
remix
security
social-provider
solid
stale
svelte
tanstack-start
tracking
version-bump
vue
wontfix
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#678
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?