Hi, I am building a chrome extension that is supposed to read and write to solid pods and therefore also needs to provide authentication.
The chrome extension by @kidehen unfortunately doesn’t solve this problem as it doesn’t use any solid functionality in the extension popup itself.
I tried multiple approaches and always hit a wall at some point.
My first approach was using a popup login which uses a popup from a solid server. However, the chrome extension’s url is not automatically added to the trusted applications which is necessary for the read and write process as explained here.
Because of that, I included the popup in the chrome extension by just generating one with solid-auth-client. The popup that asks to trust this application does come up, however, the application is named as null and an error window appears after the access has been granted.
Nevertheless, the chrome extension does get added to my trusted applications. When I start the login process again, I get the message that I have been logged in, however, no access token is returned from the process, resulting in the session object to be null. I’m not sure why there would be a difference with the popup being hosted on a solid server or in my extension.
I also managed to get the original source code of the popup.html and tried changing the necessary parts to avoid that error. However, I get another error that occurs when calling
getRegisteredRp(idp, options) from solid/oidc-rp.
I also considered letting the user log in through an external home page like @glensimister proposed, however, I am worried that the chrome extension wouldn’t be properly added to the trusted applications as the origin url would now be the one from the external home page.
Any thoughts are very welcome!