The organization plugin only a select number of server versions of the sdk?
Hello, I'm new here so sorry if I do something incorrectly 🙂
I'm coming from auth.js to better-auth and I really like the library so thanks for making it!
Now my question(s). Is it true that some endpoints for the organization plugin are only made for the client version of the SDK?
Like for example: update and delete organization?
And what is your stance on trying to do everything via the server. In my mind that is the saver route. So that you can do some validation on the server because you can never trust what the client does.
Like for example: creating a new org, making sure it doesn't exists or that the user have the not gone over the limit etc.
Hope someone can help me with these questions,
Thanks 🙂
2 Replies
For creating an org, you can pass
userId in the body when calling it from the server, which skips the auth check and simply creates an org for that user. That said, most endpoints are meant to be used through the client SDK, and whenever you use them from the server, you'll need to pass the headers.Hey, thanks for responding, after a bit of snooping around. I indeed found more "endpoints" available through the auth.api object.
I still feel it's a nicer architecture to do it on the server just because you can do more stuff around it that are not native to better auth.