Thanks Mike. Really good info. Perhaps you are right, and we should forego removing authentication. The trick with writing an extension to manage auth, is how we are implementing it. We have various needs to pass data back and forth between many systems. Some of those have poor communication. Thus the php script is handling some of that (mostly getting hostnames, doing DNS lookups, protocol types, fqdns) and then passing all those into Guacamole to create the correct connection type.
I think ultimately what I will end up doing is using the mysql auth, and just having the php script add and remove the individual db entries. Then we'll have a much easier manageable source of data, and shared/concurrent connections benefit as well! If doing that, can we then avoid the no-auth/user-mapping 'caching'? -- View this message in context: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/Connection-errors-on-no-auth-unless-logout-first-tp93p618.html Sent from the Apache Guacamole (incubating) - Users mailing list archive at Nabble.com.
