customHeader authentication

ShinyProxy
1

Do you have a minimal example of deploying the new customHeader authentication in ShinyProxy 3.2?

I am unclear if the header is sufficient or if a webservice is needed and how that interacts with the header (and group)

2

Hi

It seems we missed this post before.

Indeed adding the headers is enough, there is no need to run or configure a webservice.

As a quick example, let’s say you have the following ShinyProxy config:

proxy:
   title: My ShinyProxy
   authentication: customHeader

If you try to access ShinyProxy in a browser, you’ll be redirect to the “auth error” page.

To test the authentication, you can use curl and send the correct header:

$ curl -H "REMOTE_USER: jack" localhost:8080/api/proxyspec/
{"status":"success","data":[]}

With the header, you are now authenticated as the “jack” user.