You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 27, 2023. It is now read-only.
the client needs to authenticate on the proxy ( a good thing probably so that only the local user uses our proxy )
the proxy needs to be able to request resources as the user ( so the proxy needs to be able to open up connections with a private key of which the public key is in the users profile and which is controlled by the server ) - or we need to implement the secretary feature.
If one user has a WebID with a browser certificate, will the cors proxy be able to fetch remote resources using this certificate? Can the proxy act like some kind of handshake intermediary?
Or the platform should add generated platform cert to any WebID it manages so that when an user auth to the proxy with the browser cert, the proxy can then authenticate to the remote resource with the corresponding private key it holds locally?
Currently the proxy supports only GET requests.
The proxy also needs to be able to forward PUT, POST, DELETE, etc...
The text was updated successfully, but these errors were encountered: