Thanks Mike, I think you are heading me to the right way.
It actually works in one of my environments but in another one, I get
the following HTTP 400 error message when POSTing to /guacamole/api/tokens.
Client side: {"message":"The username must not be
blank.","translatableMessage":{"key":"APP.TEXT_UNTRANSLATED","variables":{"MESSAGE":"The
username must not be
blank."}},"statusCode":null,"expected":null,"type":"BAD_REQUEST" }
Server side: DEBUG o.a.g.rest.RESTExceptionMapper - Client request
rejected: The username must not be blank.
Config: guacamole-client 1.4.0 with:
- guacamole-auth-header-1.4.0.jar
- guacamole-auth-jdbc-postgresql-1.4.0.jar
- guacamole-auth-json-1.4.0.jar
Any idea where that could come from?
(of course, in that latter environment, guacamole-auth-json works as
planned, with a non-blank username)
Using your tip, I now submit it this kind of JSON:
#######
{
"username" : "",
"expires" : TIMESTAMP_A,
"connections" : {
"connection_A" : {
"protocol" : "rdp",
"parameters" : {...}
},
}
}
{
"username" : "",
"expires" : TIMESTAMP_B,
"connections" : {
"connection_B" : {
"protocol" : "rdp",
"parameters" : {...}
},
}
}
######
Le 13/02/2023 à 22:11, Michael Jumper - [email protected] a écrit :
No, but if you want that behaviour, you should set the username to ""
(empty string), which represents an anonymous user. The tokens for
anonymous users are stored only in memory, not in LocalStorage.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
