-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compatibility with Other OIDC Providers #45
Comments
Hello @stefanosbou, Thank you for your kind words! There are some known compatibility issues with certain OIDC providers in the current version of You can follow the progress here: GitHub Pull Request #44. |
The error you’re encountering is specifically resolved in v6. Additionally, I’ll include documentation on configuring the authentication provider that isn't specific to keycloak. |
Thanks for the quick response @garronej and for sharing the update on v6! It’s great to hear that the upcoming release will address these compatibility issues. I’ll keep an eye on #44 and look forward to the new version. Appreciate your work on this! Let me know if there's anything I can do to help test v6 when it’s ready. Thanks again! 😊 |
Well if you can provide a quick feedback confirming that everything works ok with the OIDC provider you are using it'll be great :) |
Hello @stefanosbou, |
First off, thanks for your effort in building and maintaining this library! It looks like a great solution for handling authentication in SPA applications. I’m exploring the use of this library for authentication in a Vite-powered SPA. While the documentation emphasizes Keycloak integration, I’m curious if this library also supports other OIDC providers such as Clerk or Auth0.
To test compatibility, I attempted to set up a proof of concept using the OIDC-SPA + Tanstack-router Starter template. However, I encountered the following error during initialization:
Is this library designed to work with other OIDC providers? If so, are there any additional configuration steps required to adapt it to providers other than Keycloak?
Thanks in advance for your insights!
The text was updated successfully, but these errors were encountered: