topic Active Directory Integration: Seriously very broken in Alfresco Archive

Active Directory Integration: Seriously very broken

blentz — Sat, 23 Sep 2006 04:52:39 GMT

I've tried following the steps outlined in http://wiki.alfresco.com/wiki/Configuring_NTLM and no matter how hard I try to enter in my domain name and enter the IP addresses (or hostnames) of my Active Directory servers, it always throws an exception: "Failed to find domain controller or browse maste

Re: Active Directory Integration: Seriously very broken

blentz — Sat, 23 Sep 2006 06:06:38 GMT

The LDAP stuff works, but I still get the error "File server configuration error, Wrong authentication setup for alfresco authenticator". I'd love for someone to help me get this one resolved.

JAAS still broken.
NTLM still broken.

None of the LDAP synchronziation stuff works, either. When I modify scheduled-jobs-context.xml and add the triggers according to http://wiki.alfresco.com/wiki/Enterprise_Security_and_Authentication_Configuration#LDAP_People_synchronisation, things blow up. The file says "Triggers should not appear here" yet the Enterprise Security doc gives an example doing exactly that. I get errors like "Error creating bean with name 'ftsIndexerTrigger' defined in class path resource" when I try this.

Re: Active Directory Integration: Seriously very broken

andy — Tue, 26 Sep 2006 08:40:44 GMT

Hi

See

config\alfresco\extension\ldap-authentication-context.xml.sample

You should use this example to set up LDAP.
There are other examples for NTLM and JAAS.

The example includes registration with the scheduler - which you will have to uncomment. There is no reason to change scheduled-jobs-context.xml with 1.3 and above. However, your error suggests there is something wrong with the changes you have made to this file.

"File server configuration error, Wrong authentication setup for alfresco authenticator". This is not terminal - this means the authentication system will not support CIFS. Not all do. Only Alfresco and PassThru do unless CIFS is configured to use Kerberos on Windows.

What you need to configure for authentication depends on what you want to do.

The wiki docs are due for updating in the next few weeks foe 1.4. JAAS, NTLM, LDAP, or PassThru all work when configured correctly.

Regards

Andy

Re: Active Directory Integration: Seriously very broken

blentz — Tue, 03 Oct 2006 14:11:23 GMT

What about kerberos on linux? Why doesn't that work?

Re: Active Directory Integration: Seriously very broken

andy — Tue, 10 Oct 2006 08:14:02 GMT

Hi

You can use JAAS/Kerberos authentication on linux and against a linux Kerberos server. The default kerberos/JAAS implementation should be fine. If not, you can use any other Kerberos JAAS provider. The question is "Does you client support Kerberos tickets?". Which it will, if it is IE.

You need to set Kerberos up and configure it. Single sign on against a non active directory/windows configuration is another issue. I believe it is possible but I (personally not we Alfresco) have not set it up and tested it. The client application is import.

If you are still having trouble I suggest you get in touch with Support
http://www.alfresco.com/services/support

There are many people authenticating against AD and extacting users and groups from AD using LDAP.

Regards

Andy

Re: Active Directory Integration: Seriously very broken

prajjwal — Mon, 02 Jul 2007 08:23:37 GMT

Hi,

I noticed that this post is quite old. Still, as I was getting the same kind of problem, and had to troubleshoot the issue for some time to get the 'domain controller not found' error gone, I am posting here, hoping it might be useful. (I am still troubleshooting– I am getting a 'Passthru server list already configured' error now on Alfresco 2.0, but I am still trying to fix that one).

When I got the domain controller not found error, I did a tcpdump on my interfaces and noticed that netbios broadcasts were being sent to the loopback interface. Changing the /etc/hosts to map the public ip address of the server to the hostname (alfresco.mytestdomain.com), I was able to get rid of the first error. Previously, alfresco.mytestdomain.com was mapped to 127.0.0.1 in /etc/hosts, which is why broadcasts were being sent to the loopback interface only, and I was getting the domain controller not found issue.

Re: Active Directory Integration: Seriously very broken

meansartin14 — Tue, 13 Jan 2009 20:39:11 GMT

I have started a thread that I hope to eventually turn into a AlfrescoWiki page for how to configure Active Directory authentication for both CIFS and the Web Interface in Alfresco Labs 3c.

Please see my thread:
[ERROR]Alfresco Engineers: CIFS auth does not work. Sugg?

Please come join in the discussion, or at least subscribe to the thread. I want to try to get everyone having these types of issues into the thread so that we can get a large collection of experiences and configurations.

We WILL find the answer for how to enable Active Directory authentication with CIFS in Alfresco!!