I agree. If they're trying to use the extension with 0.9.12, they would be missing that URL formatting fix, which would result in the token returned by CAS never reaching the auth provider. The auth provider would then redirect the user to CAS, which would redirect back to guac (already authenticated), then back to CAS (still no token), then back to guac ... etc.
On Thu, Jul 13, 2017 at 7:07 AM, Nick Couchman < [email protected]> wrote: > So, we'll see what comes out of it, but I'm reasonably certain that the > CAS infinite redirect issue is because the user took the module from 0.9.13 > and is trying to load it with a base Guacamole version of 0.9.12. User > stated that they modified the version on the CAS module to make it load > with 0.9.12 - there were a couple of commits to the main Guacamole client > code to deal with the redirection, that I believe they are probably hitting > an incompatibility between those versions. > -Nick > > On Thursday, July 13, 2017, 9:01:16 AM EDT, Nick Couchman < > [email protected]> wrote: > > I did see that issue and had not responded to it, yet - just replied, so > we'll see if we can track that one down, and I'll do a little more testing > here on my systems and see if I can reproduce it. Anyone else used the CAS > module with either success or failure? > -Nick > > > On Thursday, July 13, 2017, 1:51:19 AM EDT, James Muehlner < > [email protected]> wrote: > > I'm generally feeling pretty good about this release, but I do have some > reservations in that there is a report of an infinite loop with the CAS > authentication system (in the scope discussion thread), which has yet to be > addressed. > > I don't believe that I have any way to test CAS myself but I would feel a > bit uncomfortable giving my approval until it's verified that this is not > an issue. > > Nick - have you seen this report? You're probably in the best position to > evaluate whether this is an issue or not. > > James > > On Mon, Jul 10, 2017 at 6:16 AM, Nick Couchman < > [email protected]> wrote: > > > +1 > > On Monday, July 10, 2017, 1:43:35 AM EDT, Mike Jumper < > > [email protected]> wrote: > > > > Hello all, > > > > The first release candidate for Apache Guacamole 0.9.13-incubating has > been > > uploaded and is ready for VOTE. The draft release notes (along with links > > to artifacts, signatures/checksums, and updated documentation) can be > found > > here: > > > > http://guacamole.incubator.apache.org/releases/0.9.13-incubating/ > > > > The git tag for all relevant repositories is "0.9.13-incubating-RC1": > > > > https://github.com/apache/incubator-guacamole-client/tree/0. > > 9.13-incubating-RC1 (commit de12b683d746129ddc8b34425ed6e40b618c91d6) > > https://github.com/apache/incubator-guacamole-server/tree/0. > > 9.13-incubating-RC1 (commit ca3563a38e6416a6cde7f208dc9827c512227888) > > https://github.com/apache/incubator-guacamole-manual/tree/0. > > 9.13-incubating-RC1 (commit a1a4ee64dd00217905288ac1d902713b0298c03b) > > > > Build instructions are included in the manual, which is part of the > updated > > documentation referenced above. For convenience: > > > > http://guacamole.incubator.apache.org/doc/0.9.13-incubating/ > > gug/installing-guacamole.html > > > > Maven artifacts for guacamole-common, guacamole-common-js, and > > guacamole-ext can be found in the following staging repository: > > > > https://repository.apache.org/content/repositories/ > orgapacheguacamole-1007 > > > > Source and binary distributions (also linked within the release notes): > > > > https://dist.apache.org/repos/dist/dev/incubator/guacamole/0 > > .9.13-incubating-RC1/ > > > > Artifacts have been signed with the "[email protected]" key listed in: > > > > https://dist.apache.org/repos/dist/dev/incubator/guacamole/KEYS > > > > Please review and vote: > > > > [ ] +1 Approve the release > > [ ] -1 Don't approve the release (please provide specific comments) > > > > This vote will be open for at least 72 hours. > > > > Here is my +1. > > > > Thanks, > > > > - Mike > > >
