On Wed, May 5, 2021 at 1:50 PM Mike WW <[email protected]> wrote:
> 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. ...
>
You'll have to make at least some changes to that JSON, as its expiration
timestamp is in the past ("1446323765000" is 2015-10-31 20:36:05 UTC). It
will be ignored by guacamole-auth-json as expired. If you are getting the
same encrypted data back, that's a good sign - you can probably just edit
the JSON to have a non-expired timestamp.
Michael Jumper
CEO, Lead Developer
Glyptodon Inc <https://glyp.to/>.
