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
As of #13832, app access will preserve the path portion of a URL through the login process when an unauthenticated user tries to access an app access URL. This should include both the path and any query string, but it currently discards the query string.
Current behavior:
When accessing the URL as an unauthenticated user, the first thing teleport does is issue a redirect to the /web/launch for the app, and it includes the path as a query string. The ?query=bar from the initial URL is not included in the redirect.
Expected behavior:
As of #13832, app access will preserve the path portion of a URL through the login process when an unauthenticated user tries to access an app access URL. This should include both the path and any query string, but it currently discards the query string.
Current behavior:
When accessing the URL as an unauthenticated user, the first thing teleport does is issue a redirect to the /web/launch for the app, and it includes the path as a query string. The
?query=bar
from the initial URL is not included in the redirect.If I manually add in the URL escaped query string, the rest of the login flow works and preserves it the rest of the way through:
I believe this means that this can be fixed with a one-line change to simply add an escaped
?
and URL.Query.https://github.com/gravitational/teleport/blob/v10.2.0/lib/web/app/handler.go#L387
Bug details:
gz#6770
The text was updated successfully, but these errors were encountered: