[ 
https://issues.apache.org/jira/browse/GUACAMOLE-808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18093920#comment-18093920
 ] 

David Bateman commented on GUACAMOLE-808:
-----------------------------------------

Ok, this is driving me a bit crazy... In the function 
indexRouteConfig.js($routeProvider) any unconfigured route automatically 
redirects to the homepage... I initially thought my code worked as I used one 
of the routes that was in the $routeProvider, but if I try 
"/#/settings/sessions" for example as the page I attempt to connect to before 
authentication, the $routeProvider will always redirect me to the homepage...

It seems to me the return to the homepage on reauthentication is pretty deeply 
coded into the AngularJS. Is this worth pursuing ? 

> Support redirecting to originally requested URL after successful SSO login
> --------------------------------------------------------------------------
>
>                 Key: GUACAMOLE-808
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-808
>             Project: Guacamole
>          Issue Type: Improvement
>          Components: guacamole, guacamole-auth-sso-cas, 
> guacamole-auth-sso-openid, guacamole-auth-sso-saml
>            Reporter: Parth Mishra
>            Priority: Minor
>
> Upon successful authentication via OIDC, the user is returned to the redirect 
> URI (e.g. {{https://myserver.com/guacamole/}}) even if they were requesting 
> another Guacamole resource such as a Connection link. It would be nice if the 
> user could be routed to the requested resource after successful 
> authentication.
> This way, if they were to click a direct link to a guacamole Connection they 
> have access too, the successful authentication via the IDP can reroute them 
> directly to the requested connection URL rather than the guacamole UI. 
> Typically this is done with encoding the request URL with the "state" 
> parameter of OIDC and verifying with the nonce. 
> This feature could be really useful for relying on custom frontends without 
> having to modify or reimplement the web app.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to