-
Notifications
You must be signed in to change notification settings - Fork 210
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
Is it possible to use oidc-client-ts in service worker? #398
Comments
This library only supports SSR (without a |
i am now closing this, if you do not agree please comment here... |
I would like to see this working in service workers and chrome extensions using manifest v3 as well. Can you reopen the issue? Anything speaking against supporting this? |
I am struggling with the auth in manifest v3 service worker since it was released. It would be really nice if this was supported. We would also probably want to have a new cache option. To cache inside |
I am willing to work on this, but only if inrupt/solid-client-authn-js#2202 gets resolved, otherwise it won't help my cause |
For anyone wondering about MSAL, it has similar problems supporting the service worker and manifest v3 you can also have a look at my example repo and perhaps reuse some polyfills for window object even with this OIDC lib. |
I have created a sample repo of a chrome extension using this oidc-client-ts library feedback is welcome, as I would like to make this work perfectly. I think right now it does not handle token expiration. So PR are welcome. Update: Handling token expiration fixed with Alino/OIDC-client-ts-chromium-sample@da85254 |
I would like to use oic-client-ts in service worker in chrome extension.
Be these things throw errors(window is not existent in service worker):
async signinPopupCallback(url = window.location.href, keepOpen = false) {
How to fix such things?
The text was updated successfully, but these errors were encountered: