We appreciate that you tried SuperTokens. Please find below the reply to your questions.
1- It would be difficult to expire existing JWT’s on password change (would have to implement a token blacklist).
Answer - Yea. That’s one of the downsides of using JWTs. We could implement a blacklisting feature for them, but that would require users to integrate with caching solutions as well.. we can do this eventually.
2- What would the switchover path be if Supertokens stops being maintained?
Answer- Same as what it would be to move to supertokens from another auth provider. Example of moving from auth0 to supertokens - supertokens.com/docs/thirdpartyema...
3- How could multi-tenant roles be implemented within Hasura when users are in a separate schema (or even database).
Answer- We are not sure how you mean by implemented within Hasura. Could you please elaborate?
4- Database schema is fragmented and would be hard to use.
Answer- why do you think so could you please elaborate on this as well.
And we encourage you to join our discord server to discuss your use case or send us an email at team@supertokens.com
Thanks for the feedback! For items number 3 and 4 I was hoping to find a simple "users" table in the schema so that I could easily track it in hasura : hasura.io/docs/latest/graphql/core.... Instead, supertokens provided a more complicated schema that would have taken a significant time investment to understand and manage. This is likely due to the nature of building an auth service so not a bad thing.
The nHost team does provide an open source auth solution that has a nice clean schema that works out of the box with Hasura : github.com/nhost/hasura-auth
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
We appreciate that you tried SuperTokens. Please find below the reply to your questions.
1- It would be difficult to expire existing JWT’s on password change (would have to implement a token blacklist).
Answer - Yea. That’s one of the downsides of using JWTs. We could implement a blacklisting feature for them, but that would require users to integrate with caching solutions as well.. we can do this eventually.
2- What would the switchover path be if Supertokens stops being maintained?
Answer- Same as what it would be to move to supertokens from another auth provider. Example of moving from auth0 to supertokens - supertokens.com/docs/thirdpartyema...
3- How could multi-tenant roles be implemented within Hasura when users are in a separate schema (or even database).
Answer- We are not sure how you mean by implemented within Hasura. Could you please elaborate?
4- Database schema is fragmented and would be hard to use.
Answer- why do you think so could you please elaborate on this as well.
And we encourage you to join our discord server to discuss your use case or send us an email at team@supertokens.com
Thanks for the feedback! For items number 3 and 4 I was hoping to find a simple "users" table in the schema so that I could easily track it in hasura : hasura.io/docs/latest/graphql/core.... Instead, supertokens provided a more complicated schema that would have taken a significant time investment to understand and manage. This is likely due to the nature of building an auth service so not a bad thing.
The nHost team does provide an open source auth solution that has a nice clean schema that works out of the box with Hasura :
github.com/nhost/hasura-auth