On Tue, Feb 8, 2022 at 9:18 AM Antoine G. <[email protected]> wrote:
> On 08/02/2022 10:08, Caleb Coverdale - [email protected] > wrote: > > I was wondering if there was a way I could get the connection URL’s > encoded in the same format that the auth header json uses? > > I think the question could use a little clarification. When you say, "in the same format that the auth header json uses": * Do you mean the header extension or the JSON extension? They are two different extensions. * Do you mean the path to the client, or the path that the JSON extension uses to authenticate a user? These are very different items to ask for - the path to the client is (mostly) as Antoine mentions below, a Base64 encoded representation of the identifier, type, and datasource. The path used by a JSON authentication extension is probably going to include data both in the path itself and in the body of the request in the form of an encrypted payload. > As far as I know, yes (but it should be confirmed by Guacamole > devs/maintainers). > If your connection is called "joe_10.1.2.3_3389" (because you passed the > JSON below to this Guacamole extension), you have to b64 its name + FF > char + NUL char + "json". The result would be > "/#/client/am9lXzEwLjEuMi4zXzMzODkAYwBqc29u". > > I would reference the following file: https://github.com/apache/guacamole-client/blob/master/guacamole/src/main/frontend/src/app/navigation/types/ClientIdentifier.js The path to the client is a NULL-joined combination of the connection identifier (could be name, could be numeric), the type (c for connection, g for connection group), and the data source (e.g. postgres for the PostgreSQL JDBC extension). -Nick
