[BUG] admin login loads 3 wbe's instead of all

[SanderDevisscher]

Describe the bug When I log into wbe-dev.inbo.be as admin (wbe_admin according to keycloak) I can only see 3 wbe's (In flanders fiels, westhoek & westland)

To Reproduce Steps to reproduce the behavior:

1. Go to 'wbe-dev.inbo.be'
2. Login as admin
3. See error

Expected behavior Get a list of all wbe's available as admin

Screenshots Currently deployed on UAT (9286fea381ec714508f803bfc22d0806bbe02f54):

Expected (as on PRD):

On docker (0d25a18b4a7c872f77ef6b995a85ee517dc528b6) => maybe fixed by deploying to UAT ???

[SanderDevisscher]

@LynnPallemaerts @jimcasaer can you guys confirm having the same issue when login into wbe-dev.inbo.be ?

[SanderDevisscher]

@LynnPallemaerts, @jimcasaer & @gertvanspaendonk all get a timeout after login into their admin account. While I get access to the mentioned wbe's.

[SanderDevisscher]

@mvarewyck what string/info does the app expect in case of an admin user ?

[SanderDevisscher]

Login as superuser or Regio Lier works without a hitch

[SanderDevisscher]

running the app in docker as Sys.setenv(SHINYPROXY_USERGROUPS = 'wbe_admin') or kbo = 'admin' using 0d25a18b4a7c872f77ef6b995a85ee517dc528b6 work like a charm as well.

[mvarewyck]

@mvarewyck what string/info does the app expect in case of an admin user ?

The app expects ENV variable "SHINYPROXY_USERGROUPS" equal to "WBE_ADMIN". This should be configured as such in the shinyproxy yaml file.

When running the app locally/via docker, it doesn't get info from shinyproxy. Then you can either:

• Set Sys.setenv(SHINYPROXY_USERGROUPS = 'WBE_ADMIN') before starting the app
• Start the app via runWildApp(public = FALSE, kbo = 'admin')

[SanderDevisscher]

Issue has been fixed by doing needed changes to keycloak