topic Alfresco 1.4, JBOSS, JAAS and Cifs Help required in Alfresco Archive

Alfresco 1.4, JBOSS, JAAS and Cifs Help required

mattc — Mon, 22 Jan 2007 05:08:46 GMT

HiWe are running alfresco on jboss on solaris and are having problems getting the CIFS server to run when we enable JAAS to authenticate users to the web interface.Our configurations are similar to the posting http://forums.alfresco.com/viewtopic.php?p=15413&sid=59b9f09eadae37dcc5418f8c38cec46eb

Re: Alfresco 1.4, JBOSS, JAAS and Cifs Help required

mattc — Tue, 23 Jan 2007 05:09:20 GMT

Hi

I managed to figure it out (well most of it). The first problem was that the default configuration directory had a copy of file-server-custom.xml file in the extension directory (<alfresco>/jboss/server/default/tmp/deploy/tmp*alfresco.war/WEB-INF/classes/alfresco/extension). So the one in the normal extension folder (<alfresco>/jboss/server/default/conf/alfresco/extension) was never being read. We expanded the alfresco.war file, deleted the extra file-server-custom.xml file and remade the war. Now the cifs server starts up using the file-server-custom.xml file from the normal extension folder (we also needed to remove the .sample extension from network-protocol-context.xml.sample).

Not all fixed yet but at least the cifs server is now trying to connect to the AD servers. Now I just need to configure the AD connector (which I now have working for our tomcat/alfresco install).

Is this a Bug?

Cheers

Matt

Re: Alfresco 1.4, JBOSS, JAAS and Cifs Help required

paul_jacobs — Wed, 07 Feb 2007 23:39:47 GMT

I have the same issue. Can you describe your war rebuilding solution in more detail?

Re: Alfresco 1.4, JBOSS, JAAS and Cifs Help required

prototribe — Fri, 09 Feb 2007 03:54:18 GMT

Paul,

Based on the above comments there are two file-server-custom.xml files. One in the standard "extension" directory that should be there and one that appears accidentally (maybe intentionally) bundled into the alfresco.war file. Actually there may be three if your jboss explodes war files upon deployment.

You can cheat and just edit "file-servers.xml" file, though most will say not to do that (by the time you upgrade you will have forgotten that you made that change, plus a re-deploy of the war could over-write the file).

The second is removing the offending file entirely. The exact jar commands maybe a bit off as i'm going by memory.
1. Find "alfresco.war".
2a. On unix extract the archive with "jar -xvf alfresco.war" this assumes you have your path correctly set to run the jar command.
2b. On windows, open the archive the same way via a command prompt or use an archive tool like 7-zip (my preference when I have to windows).
3. Find the file "file-server-custom.xml" and delete it.
4a. On unix re-create the alfresco.war file with "jar -cvf alfresco.war alfresco"
4b. On windows if using jar see step 4a otherwise just close the archive in 7-zip and it will prompt then save the updated version.
5. Restart jboss.

The offending path will be "alfresco\WEB-INF\classes\alfresco\extension\file-server-custom.xml" in the webapp root of jboss.

That should do the trick.