Stateless Session Management: Additional Fields for Session
Hello,
So I am trying to integrate stateless session management with BetterAuth where users sign in with a generic oauth provider (this is also managed by my company and uses Better Auth OIDC Provider plugin as well), and the general flow works as expected:
The end goal here would be that when the session data is stored, I could extend the fields to apply like an
Is there a means to do this through hooks or other methods currently?
Alternative solution would be to verify and decode the
Anyhow, just curious if there is a specific workflow for this use case that is recommended.
So I am trying to integrate stateless session management with BetterAuth where users sign in with a generic oauth provider (this is also managed by my company and uses Better Auth OIDC Provider plugin as well), and the general flow works as expected:
- User initiates sign in
- User is redirected to sign in page for provider
- After sign in / authorization, user is redirected back to application and the session data is available
sub claim that would be attached to the idToken in the session object. I have looked into the customSession plugin, but seemingly can't use that, as only the current sessionuserThe end goal here would be that when the session data is stored, I could extend the fields to apply like an
idpId to the useremail and name (in this case I just want to access the sub claim instead).Is there a means to do this through hooks or other methods currently?
Alternative solution would be to verify and decode the
idToken whenever I need this information, which I can get from the getAccessToken method, but this seems quite verbose. This may be intended though for security reasons?Anyhow, just curious if there is a specific workflow for this use case that is recommended.
