Github user mike-jumper commented on a diff in the pull request: https://github.com/apache/guacamole-client/pull/353#discussion_r245786503 --- Diff: extensions/guacamole-auth-ldap/src/main/java/org/apache/guacamole/auth/ldap/connection/ConnectionService.java --- @@ -167,18 +201,34 @@ // Parse name String name = parameter.substring(0, equals); String value = parameter.substring(equals+1); - - config.setParameter(name, value); + + // Pull out and set proxy parameters, if present + // Otherwise set the parameter. + switch(name) { + case PROXY_HOST_PARAMETER: --- End diff -- Found it! ![ancient-guac-ldap-oid-assignment-scheme](https://user-images.githubusercontent.com/4632905/50790691-7c27cc00-1274-11e9-8baa-182f9e2fb50c.jpg) Quoting the contents here for reference: > 1.3.6.1.4.1.38971 = guac > .1 = LDAP schema OID's > .1 = attribute types > .1 = guacConfigProtocol > .2 = guacConfigParameter > .2 = object classes > .1 = guacConfigGroup Using the ASF OID, assuming we end up with "1.3.6.1.4.1.18060.18", we could redefine things beneath that. Presumably: 1.3.6.1.4.1.18060.18 = Apache Guacamole .1 = LDAP schema .1 = attribute types .1 = guacConfigProtocol .2 = guacConfigParameter .2 = object classes .1 = guacConfigGroup I'm looking around to see if there is a limit on the number of numeric groups in an LDAP OID, or at least if there are examples in the wild of LDAP schemas having OIDs at least as long as those proposed above.
---