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
[auth][error] MissingAdapterMethods: Required adapter methods were missing: createUser, getUser, getUserByEmail, getUserByAccount, updateUser, linkAccount, getSessionAndUser. Read more at https://errors.authjs.dev#missingadaptermethods
This is next-auth version 5.0.0-beta.29.
We connect to Entra ID for users and accounts. We don't store users ourselves. Why does it require those methods? The adapter in question only stores sessions associated with pre-existing/pre-created users.
Auth.js adapters are very flexible, and you can implement only the methods you need, and only create the database tables/columns that are actually going to be used.
Well, clearly that's not quite the case. I have actually implemented the functions I need, and it doesn't like that. Can we please have the documentation updated to reflect the actual requirements, instead of being vague about it?
But more importantly, how can I tell it not to bother with these functions? I would like to tell it "whatever you would do without an adapter, do that". Or alternatively, implement the required functions in the adapter and then trigger next-auth's default behaviour from there. Maybe like if there's a DefaultAdapter or something, then call that, but I don't think that's a thing.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
How do I fix it requiring these methods?
This is next-auth version 5.0.0-beta.29.
We connect to Entra ID for users and accounts. We don't store users ourselves. Why does it require those methods? The adapter in question only stores sessions associated with pre-existing/pre-created users.
It's also confusing when the documentation says:
Well, clearly that's not quite the case. I have actually implemented the functions I need, and it doesn't like that. Can we please have the documentation updated to reflect the actual requirements, instead of being vague about it?
But more importantly, how can I tell it not to bother with these functions? I would like to tell it "whatever you would do without an adapter, do that". Or alternatively, implement the required functions in the adapter and then trigger next-auth's default behaviour from there. Maybe like if there's a
DefaultAdapter
or something, then call that, but I don't think that's a thing.Beta Was this translation helpful? Give feedback.
All reactions