[ 
https://issues.apache.org/jira/browse/GUACAMOLE-782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tyler Frederick closed GUACAMOLE-782.
-------------------------------------
    Resolution: Not A Problem

Found an issue with the character encoding in the guacamole.properties. Issue 
resolved.

> Redirect to CAS endpoint fails in 404
> -------------------------------------
>
>                 Key: GUACAMOLE-782
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-782
>             Project: Guacamole
>          Issue Type: Bug
>          Components: guacamole, guacamole-auth-cas
>    Affects Versions: 1.0.0
>            Reporter: Tyler Frederick
>            Priority: Major
>         Attachments: http.log, image-2019-04-26-15-01-27-446.png
>
>
> *Summary*
> When testing a basic CAS configuration with the 1.0.0 Guacamole docker 
> images, the redirect to the CAS endpoint fails with a 404. Not seeing any 
> network traffic out to the CAS server, so this appears to be erroring out on 
> the Guacamole side.
> !image-2019-04-26-15-01-27-446.png!
> *Steps to Reproduce*
>  * Pull down guacamole/guacamole:1.0.0, guacamole/guacd:1.0.0, 
> guacamole-auth-cas-1.0.0.jar, and a mysql database.
>  * Create a template GUACAMOLE_HOME with the following structure:
> {{./guacamole.properties}}
>  {{./extensions/guacamole-auth-cas-1.0.0.jar}}
>  * In the guacamole.properties above, add the CAS configuration:
> {{cas-authorization-endpoint: [https://192.168.150.140/]}}
> {{cas-redirect-uri: [http://192.168.150.132:8080/guacamole/]}}
>  * Spin up containers, ensuring to pass in the templated GUACAMOLE_HOME:
> {{docker run --name test-guacamole --link test-guacd:guacd --link 
> test-mysql:mysql -v /root/guacamole-home:/mnt/guacamole-home -e 
> GUACAMOLE_HOME=/mnt/guacamole-home -e MYSQL_DATABASE=mysql -e MYSQL_USER=root 
> -e MYSQL_PASSWORD=password -d -p 8080:8080 guacamole/guacamole:1.0.0}}
>  * Visit the guacamole web interface. You will briefly see the "Please wait, 
> redirecting to CAS authentication..." screen, before hitting the 404 shown in 
> the screenshot above.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to