"I am using the guacamole-auth-json for encrypted JSON. When building my
user.json:
{
"username" : "arbitraryUsername",
"expires" : TIMESTAMP,
"connections" : {
"Connection Name" : {
"protocol" : "PROTOCOL",
"parameters" : {
"name1" : "value1",
"name2" : "value2",
...
}
},
...
}
}
where does Connection Name exist elsewhere so it knows to relate this user
to this connection? Can I define this object so that it just connected to
the DEFAULT connection?
Do I need to send the curl FROM the IP address that I am going to be
connecting to because this in the guac doc makes it sound like maybe no"
"The resulting base64 data above, if submitted using the data parameter to
Guacamole, will authenticate a user and grant them access to the
connections described in the JSON."
Here are some details of the process I'm going through:
I am using a md5 hash of the username and the encrypt-json.sh script from
the website to sign and encode this:
{"username":"fred","expires":1660129180160,"connections":{"My
Connection":{"protocol":"vnc","parameters":{"hostname":"127.0.0.1","password":"VNCPASS","port":5900}}}}
which returns a monster hash which I then try sending with a curl command
like this:
curl --data-urlencode "data=<monster hash>" http://<my ip>:8080/api/tokens
