Oauth2 not working in shinyproxy version 2.5.0 , 2.5.1 , 2.6.0

Hello,

We are running shinyproxy webpps on AWS EC2 instance .
We are able to run shinyprioy version 2.3.0 , 2.4.0 while using oauth2

When we change shinyproxy version from 2.3.0 -> 2.5.0 on AWS EC2 instance after running commands
sudo wget downloadproxy
unlink shinyproxy.jar
ln -s shinyproxy-2.5.0.jar shinyproxy.jar
sudo service shinyproxy restart

we get the following error

Field webSecurityConfigurerAdapter in eu.openanalytics.containerproxy.auth.impl.KeycloakAuthenticationBackend required a single bean, but 2 were found:
May 16 04:50:46 ip-172-31-73-41 java[28433]: - webSecurityConfig: defined in URL [jar:file:/opt/shinyproxy/shinyproxy-2.5.0.jar!/BOOT-INF/lib/containerproxy-0.8.8.j
May 16 04:50:46 ip-172-31-73-41 java[28433]: - org.springframework.security.oauth2.config.annotation.web.configuration.ResourceServerConfiguration: defined in null

The same application.yaml file works for version shinyproxy version 2.3.0 and 2.4.0 but not for 2.5.0 and above. Could someone please help us ?

Here is our application.yaml file.

server:
useForwardHeaders: true
proxy:

title: “shreyashtoday”
logo-url: someurl
landing-page: /
heartbeat-rate: 10000
heartbeat-timeout: 60000
port: 8080
authentication: simple
admin-groups: some
oauth2:
resource-id: someid
jwks-url: someurl
users:

  • name: aa
    password: aaa
    groups: client

docker:
cert-path: /home/none
url: http://localhost:2375
port-range-start: 20000

specs:
- id: default
display-name: shreyashtestingtoday
description: “shreyashtesting for inactive users”
port: 3838

  container-cmd: ["R", "-e", "shiny::runApp('/root/content/app.R', port = 3838, host='0.0.0.0')"]

  groups: some ,something

The same application.yaml file works for version shinyproxy version 2.3.0 and 2.4.0 but not for 2.5.0 and above. Could someone please help us ?

Hi

I just tested this, and unfortunately this is a bug in the latest versions of ShinyProxy. It’s a bit a hidden feature, therefore it was not yet discovered. We will fix this in the next release.

Hello Tobia,
Thanks for your reply.
Is there any workaround for using oauth2 for shinyproxy version 2.5.0 and above ?

Hello Tobia,
Thanks for your reply.
Is there any workaround for using oauth2 for shinyproxy version 2.5.0 and above ?

Our oauth2 in application.yaml file

oauth2:
resource-id: https://someresource
jwks-url: https://api.someurl/auth/serveJwks