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

[GH-ISSUE #8593] Dashboard cannot resolve user details when userId contains provider prefix (e.g. email|id) #28453

New Issue
Closed
opened 2026-04-17 19:53:58 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-17 19:53:58 -05:00
Owner
Copy Link

Originally created by @emiryumak on GitHub (Mar 13, 2026).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/8593

Is this suited for github?

  • Yes, this is suited for github

To Reproduce

  1. Migrate users from Auth0 to Better Auth Infra (Cloud).
  2. Keep the original Auth0 user IDs (format: provider|id, e.g. email|abc123 or google-oauth2|xyz789).
  3. Open the Better Auth dashboard.
  4. Navigate to the Users list.
  5. Click on a migrated user whose ID contains |.

Result: The User Detail page fails to resolve the user.

Current vs. Expected behavior

Current behavior

Users appear correctly in the Users list, but when opening the User Detail page, the dashboard cannot resolve the user if the userId contains the | character (Auth0-style IDs such as email|id).

It looks like the ID is not parsed correctly or the request fails to match the user.

Expected behavior

The dashboard should correctly fetch and display user details regardless of whether the userId contains a | character.

Auth0-style IDs (provider|id) are a common format and should be supported, especially for migration scenarios.

Additional context

These users were migrated from Auth0, where IDs are stored in the provider|id format (e.g. email|123, google-oauth2|456).

If the provider| prefix is removed and only the raw ID is stored, the dashboard works correctly.

What version of Better Auth are you using?

1.5.5

System info

Better Auth Infra dashboard

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

Other

Auth config (if applicable)

Additional context

No response

Originally created by @emiryumak on GitHub (Mar 13, 2026). Original GitHub issue: https://github.com/better-auth/better-auth/issues/8593 ### Is this suited for github? - [ ] Yes, this is suited for github ### To Reproduce 1. Migrate users from Auth0 to Better Auth Infra (Cloud). 2. Keep the original Auth0 user IDs (format: `provider|id`, e.g. `email|abc123` or `google-oauth2|xyz789`). 3. Open the Better Auth dashboard. 4. Navigate to the **Users** list. 5. Click on a migrated user whose ID contains `|`. Result: The **User Detail page fails to resolve the user**. ### Current vs. Expected behavior ### Current behavior Users appear correctly in the **Users list**, but when opening the **User Detail page**, the dashboard cannot resolve the user if the `userId` contains the `|` character (Auth0-style IDs such as `email|id`). It looks like the ID is not parsed correctly or the request fails to match the user. ### Expected behavior The dashboard should correctly fetch and display user details regardless of whether the `userId` contains a `|` character. Auth0-style IDs (`provider|id`) are a common format and should be supported, especially for migration scenarios. ### Additional context These users were migrated from Auth0, where IDs are stored in the `provider|id` format (e.g. `email|123`, `google-oauth2|456`). If the `provider|` prefix is removed and only the raw ID is stored, the dashboard works correctly. ### What version of Better Auth are you using? 1.5.5 ### System info ```bash Better Auth Infra dashboard ``` ### Which area(s) are affected? (Select all that apply) Other ### Auth config (if applicable) ```typescript ``` ### Additional context _No response_
GiteaMirror added the lockedbug labels 2026-04-17 19:53:58 -05:00
GiteaMirror commented 2026-04-17 19:54:00 -05:00
Author
Owner
Copy Link

@jonathansamines commented on GitHub (Mar 20, 2026):

Hey @emiryumak just deployed a fix for this, user ids with special values should now be correctly identified.

<!-- gh-comment-id:4094511631 --> @jonathansamines commented on GitHub (Mar 20, 2026): Hey @emiryumak just deployed a fix for this, user ids with special values should now be correctly identified.
GiteaMirror commented 2026-04-17 19:54:00 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Apr 3, 2026):

This issue has been locked as it was closed more than 7 days ago. If you're experiencing a similar problem or you have additional context, please open a new issue and reference this one.

<!-- gh-comment-id:4181127637 --> @github-actions[bot] commented on GitHub (Apr 3, 2026): This issue has been locked as it was closed more than 7 days ago. If you're experiencing a similar problem or you have additional context, please open a new issue and reference this one.
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 locked
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#28453
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?