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
I am using Shiny for Python in a ShinyProxy framework. Once the user is authenticated it tries to form the web socket connection with Shiny for Python. I have a number of different users that are successfully able to connect to either R/Shiny or Shiny for Python. This user however is unable to do so though he is able to connect with R/Shiny apps. The biggest difference appears to be that this user has a very large number of SAML roles to the tune of 22,152 characters.
Are there some character limits in the headers? I perused the shiny for python github code, and there are some content-length code, however I was unable to discern if this was relevant. I know in R/Shiny many of the libraries have issues with content length. In this situation filter/modifying the cookie isn't very feasible, since I have already cleaned up the headers with the edge router. It's really between ShinyProxy and Shiny for Python that there is an issue.
The text was updated successfully, but these errors were encountered:
I am using Shiny for Python in a ShinyProxy framework. Once the user is authenticated it tries to form the web socket connection with Shiny for Python. I have a number of different users that are successfully able to connect to either R/Shiny or Shiny for Python. This user however is unable to do so though he is able to connect with R/Shiny apps. The biggest difference appears to be that this user has a very large number of SAML roles to the tune of 22,152 characters.
Are there some character limits in the headers? I perused the shiny for python github code, and there are some content-length code, however I was unable to discern if this was relevant. I know in R/Shiny many of the libraries have issues with content length. In this situation filter/modifying the cookie isn't very feasible, since I have already cleaned up the headers with the edge router. It's really between ShinyProxy and Shiny for Python that there is an issue.
The text was updated successfully, but these errors were encountered: