Uploaded image for project: 'Alfresco'
  1. Alfresco
  2. ALF-21607

Share login form doesn't appear as fallback when Kerberos is enabled

    Details

    • Regression:
      Regression

      Description

      Steps to reproduce:

      • Setup Kerberos authentication according to http://docs.alfresco.com/community/concepts/auth-kerberos-intro.html, and add it to the authentication chain, like so: authentication.chain=kerberos1:kerberos,alfrescoNtlm1:alfrescoNtlm
      • Verify that you can login automatically to Share with Kerberos SSO using a browser configured to do so, such as an Internet Explorer browser running on a machine logged into the domain.
      • Attempt to access Share using a browser which is not configured to use Kerberos, such as Chrome.

      Expected behaviour: Share login form appears.
      Actual behaviour: Share login page is loaded (/share/page?pt=login), but login form does not appear.

      The expected behaviour works fine in Alfresco Community 5.0.c, so I would consider this a regression.

      The immediate cause of the problem is that on the Share login page, it attempts to load the resource /share/service/messages_6ec063ff30c9e48d0763b05ecbd799ef.js (for example), but receives a 401 (Unauthorized) response. This means that the Javascript variable 'Alfresco' is not defined when it is used later on in some of the script tags on the HTML page, causing the login form to not appear.

      The same request to /share/service/messages_....js returns 200 OK (despite not being logged in) in an identically configured Alfresco 5.0.c.

        Attachments

          Issue Links

            Activity

            Hide
            kroast Kevin Roast [X] (Inactive) added a comment -

            Hello Seth, thanks for raising this issue, we have a fix that is currently in testing, thanks!

            Show
            kroast Kevin Roast [X] (Inactive) added a comment - Hello Seth, thanks for raising this issue, we have a fix that is currently in testing, thanks!
            Hide
            kroast Kevin Roast [X] (Inactive) added a comment - - edited

            The fix has been verified, I will keep you informed on the merge of the changes to public branch for Community.

            Show
            kroast Kevin Roast [X] (Inactive) added a comment - - edited The fix has been verified, I will keep you informed on the merge of the changes to public branch for Community.
            Hide
            syastrov Seth Yastrov added a comment -

            Hi Kevin, that's good to hear. Would it be possible for you to give me an idea of when the changes might make it into the public branch for Community, or if that's not possible, provide a patch?

            Show
            syastrov Seth Yastrov added a comment - Hi Kevin, that's good to hear. Would it be possible for you to give me an idea of when the changes might make it into the public branch for Community, or if that's not possible, provide a patch?
            Hide
            kroast Kevin Roast [X] (Inactive) added a comment -

            Due to release stability testing on trunk, the merge looks a few weeks away.

            However, since it is a community raised issue I can provide a patch for now no problem!

            Show
            kroast Kevin Roast [X] (Inactive) added a comment - Due to release stability testing on trunk, the merge looks a few weeks away. However, since it is a community raised issue I can provide a patch for now no problem!
            Hide
            kroast Kevin Roast [X] (Inactive) added a comment -

            See attached file.

            Show
            kroast Kevin Roast [X] (Inactive) added a comment - See attached file.

              People

              • Assignee:
                closedissues Closed Issues
                Reporter:
                syastrov Seth Yastrov
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Date of First Response: