nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Alfresco 3.0 + OpenLDAP + CIFS: Working

lpiguet

After some migration pains, I was able to successfully enable Alfresco Enterprise 3.0 with users and groups coming from OpenLDAP (using clear text passwords), and a working CIFS.

I thought I would post this here. If people are interested, post a reply and I'll post more detailed steps and instructions.

Cheers,
Laurent

Find more posts tagged with

Comments

vinuraga

Hi

Am using Alfresco 3.0 + Active directory + CIFS am getting " No PassthruDetails for WSNB1 " when am trying to access through CIFS,

If you send me the configuration that you made i will try for my case if it works it will be good.

Thanks in Advance,

Vinod Raga
Cignex Technologies
India

lpiguet

Ah! I forgot to mention I am NOT using passthrough authentication…

mrojas73

Ah! I forgot to mention I am NOT using passthrough authentication…

Do you have chaining working for the local admin account?

tgck

…
I thought I would post this here. If people are interested, post a reply and I'll post more detailed steps and instructions.

Did you adapt you ldap schema and redirect the cifs session against ldap?
I would like to see your solution.

Thanks,

Torsten

vinuraga

Hi,
Even I would like to know how you have configured CIFS to authenticate thru LDAP.
Can you please share the files that you have configured to achive CIFS authentication via LDAP.

Vinod Raga
Cignex Technologies
India

lpiguet

Ok, let me get this ready, I'll post.

tretyak999

Hi,

I'm also very excited how did you managed to make it work!

Thanks in advance!

Peter

kdperuta

great! me and a lot of other people are waiting for this!

vinuraga

Hi,

I have changed my alfresco version to 2.1.2 + Active Directory + Cifs,
it is working fine now, but still problem with Alfresco 3.0 version.

Vinod Raga
Cignex Technologies
India

mrojas73

So the OP never told us how he got it working I guess?

mindthegab

Any gotchas here?

I'm having problems with share and searching users…

Strange way of managing community expectations though, why don't you just share your findings? (talking to the starter of this topic)

Thanks in advance for the effort anyways…!

mrojas73

After some migration pains, I was able to successfully enable Alfresco Enterprise 3.0 with users and groups coming from OpenLDAP (using clear text passwords), and a working CIFS.

I thought I would post this here. If people are interested, post a reply and I'll post more detailed steps and instructions.

Cheers,
Laurent

Nonsense post, thank you for nothing.

cyberheap

bump…

Anyone successfully configured the mentioned setup?

I have the same setup, and authentication works fine (chaining: Alfresco + LDAP).

CIFS works for Alfresco users, but not for the ones in OpenLDAP.

Is it even recommendable(possible) to enable CIFS with OpenLDAP+LDAP,
or would it be better to use something like Kerberos or CAS?

Thanks,
Primoz

scott_holliday

Anyone know if this is possible yet?

Specifically with Alfresco 3.2?

ghilteras

it doesnt.

alfresco community edition 3.2 doesnt work on openldap because it ignores directives you pass on properties

if you'd download the latest nightly build with the same properties that doesnt work on 3.2 it would work instantly.

problem is that the latest nightly is not a stable version

i wonder if there is a way to hotfix the community version 3.2 uploaded on the website in order to make it read custom configurations from global properties, so we could use a stable and working version of community alfresco + ldap

cheers

brice

…

if you'd download the latest nightly build with the same properties that doesnt work on 3.2 it would work instantly.

…

I had to do the same with alfresco.war (schema 2338) to allow language extension to be taken into account using web-client-custom-config.xml

ghilteras

i tried to copy the latest alfresco.war on the 3.2 community edition but still it ignores anything related to ldap authentication/syncronization written in both

tomcat/shared/classes/alfresco-global.properties
and
tomcat/shared/classes/alfresco/subsystems/Authentication/ldap/ldap-authentication.properties
and
tomcat/webapps/alfresco/WEB-INF/classes/alfresco-global.properties

it's just impossible to make alfresco read any of them.

upon authentication i always get a general error:

16:51:18,310 ERROR [org.alfresco.web.scripts.AbstractRuntime] Exception from executeScript - redirecting to status template error: 09060004 Login failed
org.alfresco.web.scripts.WebScriptException: 09060004 Login failed

THE SAME configuration works perfectly on the latest build

scott_holliday

I've managed to get my LDAP users authenticating with CIFS on latest Nightly Build.
However, i had to use the following chain:

authentication.chain=passthru1:passthru,ldap1:ldap‍

Thing is the build is not stable at all and some key components of share don't work. Like uploading files.. ??

All the configurations were put into alfresco-global.properties and seem to work fine.
I based my configuration of this thread http://forums.alfresco.com/en/viewtopic.php?f=9&t=21091

Few things to note, users have to login to share before they can use CIFS (Account must not be created until this happens)
Also im receiving a heap of "web.scripts.DeclarativeRegistry" Warnings and the same Login Failed Error. Among others.

But the main thing is i achieved what i wanted to, and get LDAP authenticating CIFS.

ghilteras

it's normal that works because with the latest nightly build putting custom configuration on global properties is fixed

but it's not a stable version, i cannot use the latest build on my production env

so i repeat that what we need is just a hotfix on the stable community version to make it read global properties correctly because uploading the latest alfresco.war is not enough

dward

In the v3.2 community release, you could easily put your own settings in alfresco-global.properties.

What you couldn't do, was override the same property sets for different subsystem instances. E.g.

authentication.chain=ldap1:ldap,ldap2:ldap

And like you say, this is now fixed in HEAD. HEAD is now being stabilized for a new community release. So make sure you report any known issues in JIRAs.

ghilteras

In the v3.2 community release, you could easily put your own settings in alfresco-global.properties.

no you can't. i mean, take my case:

i just try to set up a ldap chain, without doing any override, i just want to use ldap in place of ntlm okay? simplest thing to do, so I put my configuration on alfresco-global.properties file and it JUST DOESN'T WORK

i get a standard generic "redirecting to status template error: 08300004 Login failed" error. Alfresco simply ignores everything about ldap, everything I put in the global properties file, I see on the logs it loads ldap:

INFO [org.alfresco.repo.management.subsystems.ChildApplicationContextFactory] Startup of 'Authentication' subsystem, ID: [managed, ldap1] complete

but that's it, anything related to ldap1 is ignored, the ip of the server, userid, password etc. etc. It doesnt even TRY to reach the ldap server, it just throws a clueless generic error.

but the VERY SAME configuration (the same file) works like a charm in the latest build

so what i was trying to say is why not fix the stable version? I don't want to be forced to use a latest dev version for a production env

cheers