On Sun, Dec 2, 2018 at 1:48 PM Nick Couchman <[email protected]> wrote: > > Okay, banging my head against the wall here trying to figure out what's > going on with the CAS module. At this point the redirect doesn't work at > all - the CAS module just sits on the screen with the non-translated > message: > > {{ 'LOGIN.INFO_CAS_REDIRECT_PENDING' | translate }} > > and never redirects. In the JS console I get the following: > > Failed to retrieve field with type "GUAC_CAS_TICKET" >
That specific message will occur if a custom field type cannot be used: https://github.com/apache/guacamole-client/blob/fc457c080d813044e30e1f4e8fe855d6a5900259/guacamole/src/main/webapp/app/form/directives/formField.js#L152 That's just a generic "catch", though. If an exception occurs somewhere within the promise handling (due to something now being broken in our handling of custom fields?), you could see the same result, despite the field type being correctly registered. If this is the case, other things that use custom fields like Duo or TOTP may also not work as expected. Worth rechecking. > Any ideas what might be going on here? I've looked at the various parts of > the CAS module, particularly the AngularJS stuff, and compared to OpenID to > see what differences might be there, and can't see anything obvious. I'm > sure it's something simple/stupid, but I need another set of eyes on it. > Also, has the OpenID module been tested recently to make sure it works? I > don't think I have an OpenID provider I can test against, else I would do > it myself... I have a test deployment which uses OpenID against Google - I'll recheck. > > Let me know if I can provide any additional information. I don't see > anything obviously wrong in the catalina.out file, so figure it's something > AngularJS-based that's going on. > Did this error occur in 0.9.14? If this is breaking things, and did not occur when CAS support was initially released, I'd suggest a git bisect to narrow down when it started. - Mike
