May 2008
This Readme discusses the known issues for iFolder™ 3.6 for OES 2 Linux and for the iFolder™ client for iFolder™ 3.6.
This section describes known issues for the iFolder enterprise server, Web Access server, and Web Admin server.
When you attempt to configure an iFolder user account, either it takes a longer time (90 to 20 seconds) than expected or it throws a Timeout error. In the latter case, further iFolder operations fail and you cannot create a new account until the old one is removed. Due to this partial account creation, user account details have incorrect information and certain operations throw exception error.
The workaround for this issue is:
Go to /var/simias/data/simias directory and open the Simias.config file.
Search for Context dn in the config file.
Add each sub-container or sub-context or usergroup or dynamic group one after the other.
For eg:
Context dn="ou=<prv>,o=<novell>"/
Context dn="ou=<blr>,o=<novell>"/
Context dn="cn=<usergroup>,o=<novell>"/
Context dn="cn=<dynamicgroup>,o=<novell>"/
Make sure that for all the above serach context, read rights are given for the iFolder proxy users.
Save the file and restart Apache to load the new contexts with appropriate users.
An automatic pre-beta 5 to FCS upgrade is not supported. To upgrade the iFolder server from a prior beta version (beta1 to beta 4) to FCS, follow the steps given below:
Right-click the desktop and select .
At the command prompt, enter rpm -Uvh --force ifolder3-enterprise-3.6.0.xxxx-1-2.1.i586.rpm
NOTE:Replace xxxx with the FCS build revision number.
IMPORTANT:The format for the version number for the iFolder enterprise server RPM is 3.6.0.xxxx. For example, ifolder3-enterprise-3.6.0.7226.1-2.
When you convert a normal folder to an iFolder by using Nautilus, the change in the icon is not reflected if your iFolder client runs on SLED 10. This issue is fixed on SLED 10 SP1.
The iFolder 3.6 installed and conffigured on NSS volumes fails to function after the server upgrade from OES 1 SP2 to OES2. The potential cause is that the Simias.config file created during the upgrade is missing.
The workaround is:
Take the file system backup of iFolder 3.2 data store and Simias.config file.
Default location is /var/lib/wwwrun/.local/share/Simias.config.
Ensure that you know the iFolder Proxy user password.
Open a terminal console and enter /opt/novell/ifolder3/bin/simias-server-setup --upgrade.
Follow the on-screen instruction to manually upgrade the server.
In a Multi-server setup, where a master server connected to two slave servers, and an iFolder user is removed from LDAP, the iFolders that belong to that user are not displayed as orphans.
When you attempt to upload large files of size more than 1 GB, upload is cancelled and iFolder throws an exception.
To resolve this, you must install the latest Mono® and XSP patches which is available through Novell Customer center.
To apply the patches,
Install iFolder with OES 2.
During OES 2 configuration, select .
Complete the Novell Customer Center System Registration procedure.
Continue with the remaining steps for configuration.
Once you complete the configuration, open to resolve the dependencies and apply the Software patches available on your machine.
In the Web Admin console, if the LDAP context is changed, then the proxy user does not have the rights to browse the user identity in the context. The workaround is to execute simias-server-setup --updateLdap in the terminal console. The command line utility is available at /opt/novell/ifolder3/bin.
If you log in to the iFolder server using the thick client, log out, then attempt to convert a normal folder to an iFolder by using Nautilus, you can see that the folder is converted to an iFolder. This is because Simias runs even after your exit from the client, allowing the Nautilus plug-in to perform all the operations equivalent to the iFolder client.
Irrespective of the status of the data store, both the and buttons are active when you select a data store. In other words, even if the data store is enabled, the button stays active and when the data store is disabled, the button stays active. When you select any part of the data store and click the button (if the data store is enabled), both the buttons becomes inactive. This does not affect any functionality.
During iFolder configuration via YaST, installing an iFolder slave server into an existing domain does not update the Simias.config file with the given LDAP search context unless it is same as that of the master iFolder server.
The workaround for this issue is that to update the LDAP search context in the page of the Web Admin console and execute simias-server-setup --updateLdap in the terminal console. The command line utility is available at /opt/novell/ifolder3/bin.
When an iFolder user transfers the ownership of an iFolder to you, and subsequently you attempt to delete that iFolder through Web Access, an exception stack trace is displayed in the browser.
When you transfer the ownership of an iFolder to a new member, and subsequently you attempt to remove your membership from that iFolder, an exception stack trace is displayed in the browser.
The first attempt to log in to both Web Admin and Web Access fails when the server is first configured. The potential cause for this issue is the prolonged time duration taken to complete the LDAP sync. The workaround for this issue is to restart the Apache server.
The Redirect URL configured for iFolder Web consoles fails when you access iFolder through NetWare Access Gateway.
The SSO with identity injection to the iFolder Web Access fails if the previous session cookie exists in the machine.
This section describes known issues for iFolder client for Linux.
An automatic pre-beta 5 (beta1 to beta 4) upgrade to FCS is not supported. To upgrade the iFolder client from a prior beta version to FCS, you must uninstall the existing client and install the new version of the iFolder client software.
To force upgrade the existing client,
Right-click the desktop and select .
At the command prompt, enter the following commands in the order given:
NOTE:Replace xxxx with the FCS build revision number.
IMPORTANT:The format for the version number for the iFolder client and the iFolder enterprise server RPMs is 3.6.0.xxxx. For example, ifolder3-3.6.0.7226.1-2.
Modifying any file in an encrypted iFolder performs a full sync to the iFolder server, instead of synchronizing only the changes.
This section describes known issues for iFolder client for Windows.
An automatic pre-beta 5 (beta 1 to beta 4) upgrade to FCS is not supported. To upgrade the iFolder client from a prior beta version to FCS, you must uninstall the existing client and install the new version of the iFolder client software.
IMPORTANT:The format for the version number for the iFolder client exe is 3.6.0.xxxx. For example, ifolder3-3.6.0.7226.1-2.exe
It takes long hours to upload multiple files of total size larger than 1 GB. The workaround is to apply the latest Mono® and XSP patches to iFolder.
To apply the patches, see the workaround described in Section 2.6, Large File Upload Fails.
If you create an encrypted iFolder through the Web Access console or Linux client and log in to the Windows client, but do not provide a passphrase at the time of login, then you attempt to download the iFolder from the Windows client, iFolder downloads the encrypted iFolder as it is without prompting for the passphrase. It also fails to synchronize any files in the downloaded iFolder.
When you attempt to migrate iFolder 2.x to 3.6, the Migration Wizard randomly throws exception error even though it successfully migrated to iFolder 3.6.
Modifying any file in an encrypted iFolder performs a full sync to the iFolder server, instead of synchronizing only the changes.
If you install the iFolder Windows client and create a new account, then click to locate a folder to upload, iFolder crashes and throws an error message.
The workaround for this issue is to uninstall iFolder and .NET, and install them again.
When you attempt to change the server IP address by option, the dialog box does not show the change you made.
When you right-click any normal folder, the option is not available in Windows Explorer.
For more information about the iFolder 3.6, see the iFolder 3.6 Documentation site
The following sources provide additional information:
In this documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path.
A trademark symbol (®, ™, etc.) denotes a Novell trademark; an asterisk (*) denotes a third-party trademark.
Novell, Inc., makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc., reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.
Further, Novell, Inc., makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc., reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export, or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. Please refer to Novell International Trade Service Web Page for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals.
Copyright © 2007 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.
Novell, Inc., has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at Novell Legal Patents Web Page and one or more additional patents or pending patent applications in the U.S. and in other countries.
For Novell trademarks, see the Novell Trademark and Service Mark List.
All third-party trademarks are the property of their respective owners.