[
https://issues.apache.org/jira/browse/GUACAMOLE-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17365280#comment-17365280
]
David Young commented on GUACAMOLE-1218:
----------------------------------------
Groan. Chris, I tried your php with no difference between php output and what I
was getting from the encrypt.json.sh bash script from
[https://github.com/apache/guacamole-client/blob/master/extensions/guacamole-auth-json/doc/encrypt-json.sh]
.
Mike, I changed the "expires" to "1746323765000", and that didn't resolve
things for me either.
Regarding the key, I am simply (at this point) re-using the key from
[https://github.com/apache/guacamole-client/tree/master/extensions/guacamole-auth-json]
. It is lowercase in guacamole.properties (json-secret-key:
4c0b569e4c96df157eee1b65dd0e4d41) and uppercase when I run it as a param to
encrypt-json.sh .
Thanks gents. I'm not quite sure where to from here.
> Move guacamole-auth-json into the main project.
> -----------------------------------------------
>
> Key: GUACAMOLE-1218
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1218
> Project: Guacamole
> Issue Type: New Feature
> Components: Documentation, guacamole-client
> Reporter: Chris Wheeler
> Assignee: Mike Jumper
> Priority: Minor
> Fix For: 1.4.0
>
>
> guacamole-auth-json is so nice! I started to dump some major time into
> starting to develop a custom auth extension which would have ended up as
> basically this but worse, only to stumble across it just in time. Why not
> distribute it as a binary and document it on the website with the other
> first-class citizen extensions?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
