On Wed, Feb 22, 2023 at 8:42 AM Antoine G. <[email protected]> wrote: > > 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)
Yes, I think you need to provide a non-blank username. That's what the error indicates, anyway. -Nick --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
