guacamole-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Jumper <>
Subject Re: Sending private-key in json (using API to open session)
Date Wed, 01 May 2019 19:31:57 GMT
On Wed, May 1, 2019 at 5:42 AM Paul A <> wrote:

> Hi Mike
> Thanks for getting back to me, appreciate it.
> I have put \n at the end of each line – and confirmed with 3 online JSON
> validators that its valid JSON. Yet its still not working- keeps asking for
> passphrase key.
> The issue isn’t the JSON being generated, at the moment I am manually
> doing it to confirm its working, and then passing it through your
> script to get the output and put that into
> https://<GACAMOLE>/#/?tokens
> <>
> to get the token, then passing it to https://<GACAMOLE>/#/?token=
> <>
> load the page. I am doing it this way to make sure it all works – and doing
> this exact thing with using a json that doesn’t have a key, but has a
> password works. An ssh’ing into the client machine from this exact server
> while passing this rsa_dsa key (via the ssh –I RSA_DSA file) also works
> (doenst ask for a password).
> So from this, I know the key works using ssh directly, and I know the API
> works, and the json file format works when not using a multi line key. But
> adding the 2 together fails.
> So I am stuck and frustrated as to where else I can look to a resolution.

If you are still seeing:

"ERROR o.g.g.auth.json.user.UserDataService - Received JSON is invalid:
Unexpected character ('-' (code 45)) in numeric value: expected digit (0-9)
to follow minus sign, for valid numeric value at [Source:; line: 1, column: 3]"

Then the only possibility really is that the JSON is invalid. We can take a
look at the JSON, etc., but we would of course need the full JSON. I'd

1) Setting up a temporary user on an isolated system with a private key
that you wouldn't mind sending verbatim to a mailing list
2) Encrypting, etc. the JSON with a new, temporary key for
guacamole-auth-json that you will use only for this test
3) Reproduce the problem with the above
4) Send the error(s), the data that you sent to the token service producing
those errors, and the shared key used to encrypt the JSON here.

That would be enough to take a look. Without that, all I can really do is
look at the error that says "JSON is invalid" and say "yep, your JSON is

- Mike

View raw message