Alfresco is running without Share Services

[michael_s1]

Hi,  I hope someone can help.

I have activated passthru authentication, but since doing so, I am getting the message "Alfresco is running without Share Services. See your System Administrator for more details."

I have made the same change to two servers, one running Alfresco One trial 5.1.1 and one running Alfresco Community 5.1.0 (r127059-b7).  Both are displaying the same issue.

The authentication chain is:

authentication.chain=alfinst:alfrescoNtlm,passthru1assthru,ad1:ldap-ad,ad2:ldap-ad

ntlm.authentication.sso.enabled=true

ldap.authentication.active=false

Contents of passthru-authentication-context.properties

passthru.authentication.useLocalServer=False

passthru.authentication.domain=

passthru.authentication.servers=AU\\server22.ourdomain.com,server22.ourdomain.com

passthru.authentication.authenticateCIFS=false

passthru.authentication.connectTimeout=5000

passthru.authentication.offlineCheckInterval=300

passthru.authentication.protocolOrder=TCPIP,NetBIOS

passthru.authentication.defaultAdministratorUserNames=jsmith,admin

The LDAP synchronisation is working great.  I have two because I am getting two different groups of people.

Users can sign on with no problem.  admin can sign on using the alfrescoNtlm.

If I remove passthru, the error goes away.

I am using http port 8080 and all other settings are out of the box.

In alfresco-global.properties

The line share.host is fully qualified instead of 127.0.0.1

share.host=server101.ourdomain.com

Any help or pointers appreciated.

[resplin]

‌ Instead of commenting on an old thread that appears to have resolved the issue, it is helpful if you create a new one for your specific issue. Also, do you have Kerberos enabled?

‌ and ‌ Can one of you create an issue in the ALF project at http://issues.alfresco.com with details on how exactly you configured your system? Thank you.

[darkstar1]

Ok. It'll have to be early next week sometime.

[resplin]

It is worth checking to see if the solution suggested in the issue linked by ‌ applies to the issue you are seeing.

[anon26949]

Richard Esplin Thank you very much for your comment!.. My comment is also quite old... Now everything works fine. No, Kerberos was disabled in my case. Thank you for your remarks!

Kind regards,
Aleksey Bykov.

[resplin]

Thank you for confirming that you were not using Kerberos and that it currently works for you.

[mrks_js1]

I had the same issue:

[ACE-5682] Share displays the "Alfresco is running without Share Services.See your...." message when...

authentica… 

I believe it also had something to do with the browser cache.

the real issue (if i recall correctly) is that share-config-custom has changed a bit (new api endpoint): 

<endpoint>
         <id>alfresco-api</id>
         <parent-id>alfresco</parent-id>
         <name>Alfresco Public API - user access</name>
         <description>Access to Alfresco Repository Public API that require user authentication.
           This makes use of the authentication that is provided by parent 'alfresco' endpoint.</description>
         <connector-id>alfresco</connector-id>
         <endpoint-url>http://localhost:8080/alfresco/api</endpoint-url>
         <identity>user</identity>
</endpoint>‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

compare http://docs.alfresco.com/5.0/tasks/share-change-port.html / http://docs.alfresco.com/5.1/tasks/share-change-port.html 

[darkstar1]

Thanks Markus.

I finally got around to looking at the issue today and it is down to the alfresco connector being changed.

I simply changed the api endpoint to use the cookie connector.

<endpoint>

            <id>alfresco-api</id>

            <parent-id>alfresco</parent-id>

            <name>Alfresco Public API - user access</name>

            <description>Access to Alfresco Repository Public API that require user authentication.

                         This makes use of the authentication that is provided by parent 'alfresco' endpoint.</description>

            <connector-id>alfrescoCookie</connector-id>

            <endpoint-url>http://localhost:8080/alfresco/api</endpoint-url>

            <identity>user</identity>

            <external-auth>true</external-auth>

</endpoint>

[resplin]

Thanks for letting us know.

[p_bodnar]

All right, so if your Alfresco 5.1+ is running on another port than the default one (8080) and you forget to override this new "alfresco-api" endpoint, you will receive the annoying warning (still, everything else is working, or not??). So one needs to ask whether this endpoint mechanism cannot be improved (topics for a new thread, probably):

a) Share could issue at least a warning message about that the given URL is unreachable into logs.

b) It should be possible to use placeholders in these XML configurations - that would make stuff like this much easier to configure.

What do you think?

[jpotts]

I found another case where this message is displayed.

If you have both NTLM and LDAP in your authentication chain, and you have ntlm.authentication.sso.enabled=true, when you login as an LDAP-managed user you will see the message. Additionally, you will not be able to authenticate against /alfresco/api using an LDAP-managed user. Alfresco-managed users will not see the message and will be able to authenticate against /alfresco/api.

If you change ntlm.authentication.sso.enabled to false, the problem goes away.