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

Checking if User is intended recipient of Invite is casesensetive #1031

New Issue
Closed
opened 2026-03-13 08:19:43 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-03-13 08:19:43 -05:00
Owner
Copy Link

Originally created by @SNRSE on GitHub (Apr 13, 2025).

Is this suited for github?

  • Yes, this is suited for github

To Reproduce

  1. Setup Better Auth with Organisations and email and password
  2. create a user with an Email that has upercase letters
  3. invite that user to an Organisation
  4. try to accept the invitation from this User

Current vs. Expected behavior

Right now, inviting Mail@example.com will cause an issue for the user mail@example.com when trying to accept it. For logging In the email gets converted toLowerCase so the same behaviors should happen when checking if the user is the recipient of an Invite

What version of Better Auth are you using?

1.2.5

Provide environment information

does not apply as it is an issue with the backend

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

Backend

Auth config (if applicable)

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

Additional context

No response

Originally created by @SNRSE on GitHub (Apr 13, 2025). ### Is this suited for github? - [x] Yes, this is suited for github ### To Reproduce 1. Setup Better Auth with Organisations and email and password 2. create a user with an Email that has upercase letters 3. invite that user to an Organisation 4. try to accept the invitation from this User ### Current vs. Expected behavior Right now, inviting Mail@example.com will cause an issue for the user mail@example.com when trying to accept it. For logging In the email gets converted toLowerCase so the same behaviors should happen when checking if the user is the recipient of an Invite ### What version of Better Auth are you using? 1.2.5 ### Provide environment information ```bash does not apply as it is an issue with the backend ``` ### Which area(s) are affected? (Select all that apply) Backend ### Auth config (if applicable) ```typescript import { betterAuth } from "better-auth" export const auth = betterAuth({ emailAndPassword: { enabled: true }, }); ``` ### Additional context _No response_
GiteaMirror commented 2026-03-13 08:19:44 -05:00
Author
Owner
Copy Link

@SNRSE commented on GitHub (Apr 13, 2025):

I have also created the following PR to adress this Bug : https://github.com/better-auth/better-auth/pull/2251

@SNRSE commented on GitHub (Apr 13, 2025): I have also created the following PR to adress this Bug : https://github.com/better-auth/better-auth/pull/2251
GiteaMirror commented 2026-03-13 08:19:45 -05:00
Author
Owner
Copy Link

@SNRSE commented on GitHub (Apr 13, 2025):

PR is merged so closing the issue

@SNRSE commented on GitHub (Apr 13, 2025): PR is merged so closing the issue
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
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#1031
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?