🐛 Bug Report: Unique Email Unable to Create Different Usernames #318

Closed
opened 2025-10-07 00:10:17 +03:00 by OVERLORD · 4 comments
Owner

Originally created by @trumblejoe on GitHub.

Reproduction steps

PocketID requires a unique email per username. However this is an issue when someone may have two accounts for the same user.

For example logging into Jellyfin with PocketID I have both administrator & myname as usernames. On other services behind PocketID & Reverse Proxy I may have firstinitialLastName as my username on that service.

This also creates issues for accounts for shared logins for example, parents who use multiple usernames for themselves but only have one email between themselves.

Expected behavior

I expected to be able to create a new username tied to the same email as another account & then have different logins for the underlying services.

Actual Behavior

I was unable to create my needed username & was given an appropriate error message saying so.

Version and Environment

v3.5.3 behind caddy reverse proxy on unraid.

Log Output

No response

Originally created by @trumblejoe on GitHub. ### Reproduction steps PocketID requires a unique email per username. However this is an issue when someone may have two accounts for the same user. For example logging into Jellyfin with PocketID I have both administrator & myname as usernames. On other services behind PocketID & Reverse Proxy I may have firstinitialLastName as my username on that service. This also creates issues for accounts for shared logins for example, parents who use multiple usernames for themselves but only have one email between themselves. ### Expected behavior I expected to be able to create a new username tied to the same email as another account & then have different logins for the underlying services. ### Actual Behavior I was unable to create my needed username & was given an appropriate error message saying so. ### Version and Environment v3.5.3 behind caddy reverse proxy on unraid. ### Log Output _No response_
OVERLORD added the bug label 2025-10-07 00:10:17 +03:00
Author
Owner

@stonith404 commented on GitHub:

Yeah in my opinion this doesn't make sense to implement into Pocket ID. This feature would make Pocket ID unnecessarily complicated. I even doubt that more advanced solutions like Authentik support having multiple usernames.

If you want multiple accounts on your clients you have to create multiple accounts on Pocket ID.

@stonith404 commented on GitHub: Yeah in my opinion this doesn't make sense to implement into Pocket ID. This feature would make Pocket ID unnecessarily complicated. I even doubt that more advanced solutions like Authentik support having multiple usernames. If you want multiple accounts on your clients you have to create multiple accounts on Pocket ID.
Author
Owner

@kmendell commented on GitHub:

This is my opinion, but if we were to add something like that , i feel like it introduces complexity to pocket-id which is against the principles of the project. I will have to defer to @stonith404 to see what he wants to do.

@kmendell commented on GitHub: This is my opinion, but if we were to add something like that , i feel like it introduces complexity to pocket-id which is against the principles of the project. I will have to defer to @stonith404 to see what he wants to do.
Author
Owner

@trumblejoe commented on GitHub:

I think we could maintain email uniqueness as the source of the identity,
it would be helpful to have username aliases (by using a Slice on username?). It looks like the passkey is currently
stored in my password manager under the username so this would still allow
multiple usernames per user.

On Sun, Mar 2, 2025, 9:15 PM Kyle Mendell @.***> wrote:

I think this is a common thing, no? Emails should be unique in my eyes.
For example if you sign up for a website and the email is already in use
its errors out. What i do in my case i have a custom postfix relay setup
and make email aliases for each of my users which then forwards to the
email address.


Reply to this email directly, view it on GitHub
https://github.com/pocket-id/pocket-id/issues/289#issuecomment-2693115045,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGZ55UUXGU6PV45W7R7H26L2SO3NXAVCNFSM6AAAAABYFY4LPSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOJTGEYTKMBUGU
.
You are receiving this because you authored the thread.Message ID:
@.***>
[image: kmendell]kmendell left a comment (pocket-id/pocket-id#289)
https://github.com/pocket-id/pocket-id/issues/289#issuecomment-2693115045

I think this is a common thing, no? Emails should be unique in my eyes.
For example if you sign up for a website and the email is already in use
its errors out. What i do in my case i have a custom postfix relay setup
and make email aliases for each of my users which then forwards to the
email address.


Reply to this email directly, view it on GitHub
https://github.com/pocket-id/pocket-id/issues/289#issuecomment-2693115045,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGZ55UUXGU6PV45W7R7H26L2SO3NXAVCNFSM6AAAAABYFY4LPSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOJTGEYTKMBUGU
.
You are receiving this because you authored the thread.Message ID:
@.***>

@trumblejoe commented on GitHub: I think we could maintain email uniqueness as the source of the identity, it would be helpful to have username aliases (by using a Slice on username?). It looks like the passkey is currently stored in my password manager under the username so this would still allow multiple usernames per user. On Sun, Mar 2, 2025, 9:15 PM Kyle Mendell ***@***.***> wrote: > I think this is a common thing, no? Emails should be unique in my eyes. > For example if you sign up for a website and the email is already in use > its errors out. What i do in my case i have a custom postfix relay setup > and make email aliases for each of my users which then forwards to the > email address. > > — > Reply to this email directly, view it on GitHub > <https://github.com/pocket-id/pocket-id/issues/289#issuecomment-2693115045>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AGZ55UUXGU6PV45W7R7H26L2SO3NXAVCNFSM6AAAAABYFY4LPSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOJTGEYTKMBUGU> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> > [image: kmendell]*kmendell* left a comment (pocket-id/pocket-id#289) > <https://github.com/pocket-id/pocket-id/issues/289#issuecomment-2693115045> > > I think this is a common thing, no? Emails should be unique in my eyes. > For example if you sign up for a website and the email is already in use > its errors out. What i do in my case i have a custom postfix relay setup > and make email aliases for each of my users which then forwards to the > email address. > > — > Reply to this email directly, view it on GitHub > <https://github.com/pocket-id/pocket-id/issues/289#issuecomment-2693115045>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AGZ55UUXGU6PV45W7R7H26L2SO3NXAVCNFSM6AAAAABYFY4LPSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOJTGEYTKMBUGU> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >
Author
Owner

@kmendell commented on GitHub:

I think this is a common thing, no? Emails should be unique in my eyes. For example if you sign up for a website and the email is already in use its errors out. What i do in my case i have a custom postfix relay setup and make email aliases for each of my users which then forwards to the email address.

@kmendell commented on GitHub: I think this is a common thing, no? Emails should be unique in my eyes. For example if you sign up for a website and the email is already in use its errors out. What i do in my case i have a custom postfix relay setup and make email aliases for each of my users which then forwards to the email address.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/pocket-id#318