Novell iFolder 3.8.4 and LDAP sources

[VLA]

On a further note to Chris' experience with iFolder/iPad, I have set
up a fresh installation of an OES server (SuSE 10.3 and OES 2SP3)
installing iFolder 3.8.4 and it's dependencies configured with default
configuration. I have duplicated Chris' problem by testing using the
following web address http://<ifolder IP address>/simias10/
iFolderWeb.asmx and it fails.

It should be noted that the Novell distribution of iFolder requires
the dependency of Novell eDIRECTORY as a local LDAP source for the
default installation of iFolder. I'm saying that because I'm not
familiar with the open source version as I further guess, the open
source doesn't require an LDAP source from what I've read in this
forum.

My next attempt to fix the issue was to do what Chris has done by
creating a copy of the IdentityManagement.conf in the /var/simias/data/
simias/modules directory. I experienced the same result as Chris - no
application could authenticate.

In further testing, I deleted the IdentityManagement.conf file,
restarted apache and reconfigured iFolder to use a different LDAP
source. In this case, the LDAP source was a Novell eDirectory in a
second tree. I can report from this that all is working as designed.

I can also report from a third party that their recent installation of
iFolder v3.8.4 in the same OES environment as what I am testing is
also working as designed. The difference in this third party
installation is that their OES server was configured during the
installation process to join an existing tree.

Is any of these findings helpful?

[Paul DeSousa]

Just to be clear, Novell's OES will work with AD as well. Yes, eDir is the default but during the setup you do get a choice for alternate directories. I recommend you take a look at the documentation.

Thanks

Sent from mobile device.

[VLA]

Thank you for that Paul, but using another LDAP source is not the
issue. I actually wish to use the locally installed eDIR as the LDAP
source. The reason for this decision is that iFolder does not have
any controls on who can create an iFolder (apart from manually
disabling user accounts). Provided users exist in iFolder database,
users can create an iFolder - so in an environment of thousands of
users, one could end up with an ever expanding disk usage. In our
environment, we wish to "control" who can create an iFolder. The plan
is to add another connector to our IDM and populate the local iFolder
eDIR with only users that have a particular attribute. This will
allow the syncronisation of their passwords, provisioning and de-
provisioning of iFolder accounts dynamically - no administrative
intervention.

I actually have that IDM connector working and both the iFolder Web
and thick clients work - but the iPAD app fails to authenticate, which
is the sole purpose of us using iFolder.

On Apr 20, 9:16 pm, Paul DeSousa <pauldeso...@gmail.com> wrote:
> Just to be clear, Novell's OES will work with AD as well.  Yes, eDir is the default but during the setup you do get a choice for alternate directories.  I recommend you take a look at the documentation.
>
> Thanks
>
> Sent from mobile device.
>