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

"Alfresco is running without Share Services..." message with Kerberos SSO

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Cannot Reproduce
    • Affects Version/s: 5.2
    • Fix Version/s: None
    • Component/s: Share Application
    • Security Level: external (External user)
    • Labels:
    • Environment:
      Ubuntu 14.04, Kerberos SSO
    • Triage:
      Won't Fix
    • Resolution Time Custom Field:
      65 weeks, 1 day, 8 minutes, 11 seconds

      Description

      If a user that connects to share on a Non-SSO enabled browser the "Alfresco is running without Share Services..." message appears even if the alfresco-share-services is installed.

      I applied the workaround in MNT-15500 and the message disappeared.

      In share-header.lib.js the alfresco-api is used to get this information

      // retrieve ShareServices information
            var connector = remote.connect("alfresco-api");
            var result = connector.get("/-default-/private/alfresco/versions/1/modulepackages/alfresco-share-services");
      

      It is often the case that an admin has to connect with non-SSO to login in as admin (different user that they are currently logged in with in windows) and get this message in error.
      Also for many other reasons there are options to connect when not in SSO environment, such as users connecting via vpn.

      For what I can tell it is only in this case the remote connect to alfresco-api is used, but if used elsewhere would break functionality for non-SSO users.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                closedissues Closed Issues
                Reporter:
                loftux Peter Löfgren
              • Votes:
                0 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

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