Which version of the server are you using ? Could you file defect for this with admin log and SImias log in Debug ?

Log on to the server - Go to Data Path [ def :/var/simias/data ] search for Simias.config file and manually edit the context that you want to change and restart apache for now

A bug for this exists :

https://bugzilla.novell.com/show_bug.cgi?id=605518

Would be nice to have logs in the bug as Ravi has mentioned.

I'm getting a different exception to the one in that bug. See my original message.

I could upload some log files, but first I need to remove sensitive information... Not easy, there is plenty. Suggestions?

Where should I file defect for this?

As I said, I am using iFolder 3.8.0.3 server.

I manually edited the config file, and got it to display the right contexts now in the web interface, but it's still unable to synchronize.

Hi everyone,

I have managed to fix the issue by running simias-server-setup, and making sure I entered the correct values, especially for the data folders.

It seems to me that the web interface is not able to update the LDAP configuration properly, in particular the password for the iFolder proxy.

I couldn't find it stored in the configuration file, so it must be stored somewhere else for security reasons.

Is SSL enabled between iFolder server and AD ? can you copy paste the complete error message here , if you still have that info ? Which version of AD it is 2003/2008 ??

This feature was tested during 3.8.0 release for both AD 2003/2008. If there  is a problem and we know the procedure to reproduce the same, we would like to fix the same. Since so many in the community are configuring iFolder against AD, it makes sense to take a look at this.

Unfortunately I don't have the error anymore. Sorry. I had to get it fixed ASAP, and I don´t have a server to try to reproduce now.

There is no SSL between iFolder and Active Directory. It's Active Directory 2008. It was 2003 in the initial configuration, then we upgraded 2003 to 2008 a couple of months ago, but iFolder was working fine. We did the Active Directory upgrade by demoting each Domain Controller, installing a fresh new Windows 2008 server, and promoting it to Domain Controller. No in-place upgrade. I don't believe that the problem is related to our Active Directory upgrade.

The initial configuration of iFolder server was done with version 3.8.0.0, and when trying to fix it, I upgraded it to 3.8.0.3.

The steps to reproduce should be:

1- Install iFolder and integrate it with Active Directory

2- Set up the LDAP contexts to point to an Organizational Unit

3- Rename the OU, and watch as all the users get disabled

4- Try to fix the LDAP contexts using the web interface

5- The error message should appear.

As far as i remember AD would not let you perform some operations if SSL between iFolder and AD are not enabled, specifically proxy user password reset etc..  I hope when you tried last time around, SSL was enabled.

Let me also check what is the problem here, as it did work for us when we tested in last release.

Mmmm... That's probably the problem, then.

The web interface will not store the new password for the iFolderProxy user unless it is able to successfully reset it directly.

However, we haven't configured SSL for the connection between iFolder and Active Directory, and are not planning to (it works now! :)).

So if we change anything about the iFolderProxy user, we can't fix it in the web interface, and we need to run simias-server-setup script again, or edit the configuration files directly.

So I would probably consider this a usability problem. It should be possible to change the Active Directory configuration of iFolder, even if the iFolder server itself can't reset the proxy user password.

Best regards.