Closed itsdapi closed 2 weeks ago
We could not detect a valid reproduction link. Make sure to follow the bug report template carefully.
To be able to investigate, we need access to a reproduction to identify what triggered the issue. We need a link to a public GitHub repository. Example: (NextAuth.js example repository).
The bug template that you filled out has a section called "Reproduction URL", which is where you should provide the link to the reproduction.
Depending on the reason the issue was closed, you can do the following:
In general, assume that we should not go through a lengthy onboarding process at your company code only to be able to verify an issue.
In most cases, a private repo will not be a sufficient minimal reproduction, as this codebase might contain a lot of unrelated parts that would make our investigation take longer. Please do not make it public. Instead, create a new repository using the templates above, adding the relevant code to reproduce the issue. Common things to look out for:
Anyone experiencing the same issue is welcome to provide a minimal reproduction following the above steps by opening a new issue.
We look into every issue and monitor open issues for new comments.
However, sometimes we might miss a few due to the popularity/high traffic of the repository. We apologize, and kindly ask you to refrain from tagging core maintainers, as that will usually not result in increased priority.
Upvoting issues to show your interest will help us prioritize and address them as quickly as possible. That said, every issue is important to us, and if an issue gets closed by accident, we encourage you to open a new one linking to the old issue and we will look into it.
Provider type
Authentik
Environment
Reproduction URL
not quite need i guess?
Describe the issue
Using authentik as the provider with the same user login each time will create a new user.
Turns out the return
profile
object does not contain theid
property that seems nextauth used to identify the user. And the solution is quite simple for me just editing the profile object like thisI could now see the
providerAccountId
in the database is equal tosub
returning from authentikI also dug into some other similar providers like
keycloak
and found out their provider config file is quite the same and probably not have considered this scenario.So I am guessing is this a bug or a feature?
How to reproduce
use authentik as provider
Expected behavior
Using authentik as the provider with the same user login each time will create a new user and with the default setting it will not let me login because the same email address.