Uploaded image for project: 'Sakai'
  1. Sakai
  2. SAK-18337

container login with two buttons only works for the main portal page



    • Type: Bug
    • Status: RESOLVED
    • Priority: Major
    • Resolution: Incorporated
    • Affects Version/s: 2.7.0
    • Fix Version/s: None
    • Component/s: Login
    • Labels:


      We're looking at support for CAS. But we have some users who aren't in CAS. I turned it on with two login buttons. It works OK for the main portal page. But if you go directly to a URL, you are sent to CAS. That won't work for people with local accounts.

      The attached file has a prototype patch. I doubt you want to use it as is, but it will give you an idea of what needs to be done:

      1) Login should go directly to CAS for the main portal, otherwise to xlogin.

      2) Xlogin needs the two buttons, unless it's called from the main portal.

      I do the two buttons as links. xlogin still has the local login form, but it starts out hidden. The local login button unhides the form using Javascript.This is almost certainly not the way you want to do it for real.

      Of course this means that you don't get transparent SSO into URLs, which may defeat some of the reason to use CAS. My sense is that CAS may need a way to put an extra button on it that calls back to the application. Or possibly login should check for the cookie indicating a CAS ticket, and go directly to CAS if it finds one. (Of course that could cause problems for our privileged users. They may have a CAS ticket from another application, but want to login to Sakai as an admin.)

      It seems to me that if we're serious about CAS it needs more thought.

        Gliffy Diagrams



              Issue Links



                  maintenanceteam Core Team
                  hedrick Charles Hedrick
                  0 Vote for this issue
                  2 Start watching this issue



                      Git Integration