You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for maintaining this lib! My team is using it since a while and it works just great.
We recently had a need for a custom signup flow, and we struggled to do what we wanted, ie:
Create an auth0 user from an email/password.
Perform a login on behalf of the user server-side (we don't want to prompt him for consent nor make him enter a second time his credentials).
Redirect him to a nextjs page that requires a session per nextjs-auth0.
Auth0 support advised us to use auth0 node library to create the user and then call /oauth/token to retrieve an id_token and an access_token. After some back and forth with support, we were finally able to implement something that works.
Now, the issue is we had to extract logic from nextjs-auth0 (the content of this folder, basically) to perform the following tasks:
Shape/populate the session cookie payload
Encrypt that payload
Set the session cookie
From what I could gather, these responsibilities are spread out in internal code that is not exposed by the lib (StatelessSession class, TransientStore class, to name a few).
Redefining that logic in our own codebases is sub-optimal, as creating a session falls within the responsibilities of nextjs-auth0 in our opinion. If implementation details change on this lib, we would be exposed to regressions.
Describe the ideal solution
Would that make sense to have this lib expose helpers to create a session manually?
Is there something auth0 support and our team missed to answer this workflow?
Related to #1751, which basically implies the need for an easier silent login workflow, which is highly necessary! Open to help if needed but big 👍🏼 to this issue.
Checklist
Describe the problem you'd like to have solved
Hello!
Thank you for maintaining this lib! My team is using it since a while and it works just great.
We recently had a need for a custom signup flow, and we struggled to do what we wanted, ie:
nextjs-auth0
.Auth0 support advised us to use
auth0
node library to create the user and then call/oauth/token
to retrieve an id_token and an access_token. After some back and forth with support, we were finally able to implement something that works.You can find a POC here:
https://github.com/jpb06/auth0-silent-login
Now, the issue is we had to extract logic from
nextjs-auth0
(the content of this folder, basically) to perform the following tasks:From what I could gather, these responsibilities are spread out in internal code that is not exposed by the lib (StatelessSession class, TransientStore class, to name a few).
Redefining that logic in our own codebases is sub-optimal, as creating a session falls within the responsibilities of
nextjs-auth0
in our opinion. If implementation details change on this lib, we would be exposed to regressions.Describe the ideal solution
Thank you for your time 🙇🏻
Alternatives and current workarounds
Partially related: #1207
Additional context
No response
The text was updated successfully, but these errors were encountered: