Is the 8base authentication supposed to work with the @auth0/auth0-spa-js library? Pulling down their example (https://github.com/auth0-samples/auth0-react-samples/tree/master/01-Login) and running it pointed at the domain and client id from 8base returns a 401 Unauthorized on the post to https://secure.8base.com/oauth/token after entering my email and password.
Might be a knowledge gap on my end since I’m not very familiar with auth0, but I’d love to know if there’s a way to make it work.
hey @emroussel! I don’t know if anyone on our team has played with this yet. However, hypothetically it should work. Did you hook up the Auth0 account to 8base, or set up an 8base Authentication Profile?
https://docs.8base.com/docs/8base-console/authentication/#your-own-auth0-account
Also, another option for you is authenticating users directly against the GraphQL api using the userLogin and userSignUpWithToken mutations.
@sebastian.scholl I’m still testing things out under the free plan, so I just created an 8base authentication profile.
I didn’t know about userLogin and userSignUpWithToken! I can give those a try, but it would be nice to be able to use auth0’s library to authenticate as another option.
userLogin doesn’t seem to be described anywhere in the documentation (search). Does it work the same way, just going through GraphQL?
Mike
@sebastian.scholl the login and signup mutations work, but it would be great to be able to use the auth0 sdk with the default 8base authentication profile (not sure if it works with custom auth providers) so that we can follow this tutorial from Auth0 about setting up auth in react (https://auth0.com/docs/quickstart/spa/react/01-login). Are there any technical challenges preventing this? Using the sdk is also probably more secure than storing the auth and refresh tokens we get back from the graphQL mutations ourselves (usually done in local storage or cookies, neither of which is recommended).