What is the issue: the query parametercontinue always show up after a successful SAML auth, no matter directly calling the shinyproxy server: https://shinyproxy-server/, or directly calling a specific app in the shinyproxy server: https://shinyproxy-server/app/app-name/.
Expected:
https://shinyproxy-server/ → SAML login → https://shinyproxy-server/
https://shinyproxy-server/app/app-name/ → SAML login → https://shinyproxy-server/
Actual:
https://shinyproxy-server/ → SAML login → https://shinyproxy-server/?continue
https://shinyproxy-server/app/app-name/ → SAML login → https://shinyproxy-server/?continue
-
Is this the expected behavior since Shinyproxy 3.1.1, which depends on Spring-Security 6.+?
-
The issue I encountered is quite similar to the answer from a Spring-Security contributor
-
UISecurityConfig is a class in ShinyProxy project which implements interface ICustomSecurityConfig in ContainProxy, it tries to
setRedirectStrategyso that if there is an instance ofAppRequestInfo, it should remove the query paramcontinue. However, it doesn’t.