Liferay and Alfresco doclib integration

[patil]

I saw in the link
http://wiki.alfresco.com/wiki/Doclib_Portlet#Prerequisites

Alfresco supports doclib integration only with Liferay 5.2.3
Is there any plan for it to support in the future for Liferay 6 and its future releases?

Thanks,
Patil

[mikeh]

Actually, I think those instructions are out of date now and the portlets should be fine in Liferay 6. If you come across any problems, please be sure to raise them in JIRA.

Thanks,
Mike

[patil]

Thanks Mike for confirming this.

1. Where can I get the latest instructions to do the same integration?
2. I am looking for SSO integration.
    When I put
ntlm.authentication.sso.enabled=true

in alfresco-global.properties

then the portlets are showing messages as Portlet is temporarily unavailable.

Can you please tell me what I might be doing wrong here?

If ntlm.authentication.sso.enabled=false then portlets works fine.

Thanks,
Patil

[afaust]

Hello,

unfortunately - using the standard subsystem configurations - activation of SSO on any subsystem (alfrescoNtlm, passthru or kerberos) deactivates the filter that does the remote user mapping necessary for the Liferay Portlets. This is just a configuration issue and can be safely adapted. You need to provide a custom ntlm-filter-context.xml for your subsystem of (SSO) choice, which includes the following

<property name="remoteUserMapper">   <ref bean="RemoteUserMapper" /></property>‍‍‍‍‍

for the bean "globalAuthenticationFilter" (and, if relevant for other interfaces, "sharepointAuthenticationHandler" and "webDavAuthenticationFilter").

Regards

[patil]

Hi,
Thnaks for your reply.
Do I need to change any class files?

Thanks,
Patil

[afaust]

You need to provide a custom ntlm-filter-context.xml

[patil]

This is the problem with the connector. Liferay uses X-Alfresco-Remote-User as the proxy header and if you have the header other than this then the integration will fail