- From: elf Pavlik <elf-pavlik@hackers4peace.net>
- Date: Mon, 28 Apr 2025 08:16:12 -0600
- To: public-solid@w3.org
On 2025-04-28 06:19, Sarven Capadisli wrote: > On 2025-04-28 14:02, elf Pavlik wrote: >> Do you have this web browser extensions use case captured in LWS UCs >> repo? To be honest I'm to familiar with how they work. For example >> what is used as a `redirect_uri`? > > Contextual Interactions via Native User Agent or Add-on: > > https://github.com/w3c/lws-ucs/issues/55 > > As I understand it, currently browser extensions can use dynamic client > registration and use the location at the time of initiating the login > process as the redirect URI. With static client registration, this URI > will be validated against the redirect URIs specified in the Client ID > Document, and here is where the flow breaks for the case of an > extension. Thanks Sarven, this is very helpful for me to start understanding your use case! I made a typo in my previous email, I'll blame it on writing it at 6AM, I'm NOT familiar with nuances of browser extensions. I started doing some searches and it may require some more research. For example Chrome/Chromium extensions seem to use chromiumapp.org for redirect urls. https://m2kdevelopments.medium.com/25-understanding-chrome-extensions-oauth-2bd175964384#c7b4 In Firefox I found this post with 0 replies https://discourse.mozilla.org/t/how-to-integrate-google-oauth-for-calendar-access-in-firefox-extension-previously-successful-in-chrome/134818 Do you know how many people in Solid community, besides you, have experience with developing browser extensions? Cheers!
Received on Monday, 28 April 2025 14:16:20 UTC