Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SHINYPRIXY_USERNAME is not passed when using minimum-seats-available #546

Open
faridovski opened this issue Feb 3, 2025 · 2 comments
Open
Labels

Comments

@faridovski
Copy link

In order to shorten the startup time of my shiny apps, I have activated minimum-seats-available. I realized that the allocated pod does not contain the ENV variable (SHINYPROXY_USERNAME).
More details:

  • shinyproxy version 3.1.1
  • container backend: k8s cluster
  • Authentication: OpenId (keycloak)
@RespiceFinem
Copy link

Following version 3.1.0, I had this same issue.

I figured out how to extract the USERID and the USERGROUP from this and other resources:
https://support.openanalytics.eu/t/passing-username-and-groups-as-http-headers-in-3-1-0/2747/2

Today, I extract the USERID in our application with

shinyproxy_user_id <- session$request$HTTP_X_SP_USERID

Hope this helps

@mnazarov
Copy link
Member

mnazarov commented Feb 4, 2025

It is indeed specific to the pre-initialized containers, as documented in https://www.shinyproxy.io/documentation/configuration/#container-pre-initialization-and-sharing (see "Before using this feature, make sure to understand the following...")

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants