Hi
Thanks for replying quickly. What about the encoding of the data, and
encrypting it with the key? Before you can send data to that URL (same as
what we send ours to), you need to do those 2 things, which is done as an
example with the encrypt-json.sh file (provided by Mike)
I gave it a go though I tired to just put some data and got this in
postman:
{
"message": "Permission denied.",
"translatableMessage": {
"key": "Permission denied.",
"variables": null
},
"statusCode": null,
"expected": [],
"type": "INVALID_CREDENTIALS"
}
And this in the log file:
[http-nio-8080-exec-20] WARN o.a.g.r.auth.AuthenticationService -
Authentication attempt from [ 172.19.198.2] for user "paul" failed.
-----Original Message-----
From: sciUser [mailto:[email protected]]
Sent: Friday, 26 April 2019 5:10 PM
To: [email protected]
Subject: Re: Sending private-key in json (using API to open session)
How we do it:
We use curl to post :
curl -X POST -H 'Content-Type: application/x-www-form-urlencoded' -d
'username=SOMEUSERNAME&password=SOMEPASSWORD'
https://<Guacamole>/guacamole/api/tokens
This will generate a one time token for that user to login with then it
will expire, but the connection will remain as long as the session is
active in the browser. The return/redirect link should look like this:
https://<Guacamole>/guacamole/#/client/?token=5AD2069FD0F6788848BBE23B6095
816EA2B5CEBB1EF07F76051010E050C70063
Our Provisioning system does all this on the fly and manages Guacamole
directly.
Hope this helps.
Thank You
--
Sent from:
http://apache-guacamole-general-user-mailing-list.2363388.n4.nabble.com/
