Hi, I'm dealing with the same situation having used the exact same reference settings (json-secret-key and auth.json file) just in an attempt to get it working, and I'm getting the exact same signed and encrypted response (Ez9K+nkHjuEAWq...8sIYw==).
I've attempt removing line breaks with `tr -d '\n'` but while this works the resulting encrypted block still doesn't work for me. What method did you use? I have downloaded both 1.3.0 server and client from their "Apache" (so they match, and not from glyptodon) GitHub sites, successfully compiled both with Maven, installed and started the server, deployed Tomcat and the client successfully and tested with BasicFileAuthentication and the user-mapping.xml. copied guacamole-client-master/extensions/guacamole-auth-json/target/guacamole-auth-json-1.3.0.jar to GUACAMOLE_HOME/extensions (/usr/share/tomcat/.guacamole/extensions in my case) added json-secret-key: 4c0b569e4c96df157eee1b65dd0e4d41 to guacamole.properties I saw in the logs (/var/log/messages) that "Encrypted JSON .." was "loaded" on Tomcat restart but I'm not able to get a successful authentication yet. Did it matter that the encrypt.json.sh encrypted block was different from the reference example in the README on the GitHub site? What method did you use to remove the line breaks? Any help/ideas greatly appreciated. -- Sent from: http://apache-guacamole-general-user-mailing-list.2363388.n4.nabble.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
