LDAP user names must contain only valid alphanumeric characters 0 - 9 and upper-case and lower-case letters (A-Z). User names that contain ASCII characters and special characters (for example, / \ * ? " < > : | ) cannot be used as Filr user names. If your LDAP directory includes user names with these characters, they synchronize to Filr, but the associated users cannot log in.
These characters cannot be used in a Filr user name because a Filr user name becomes the user’s workspace title, and the workspace title becomes an element of the hierarchical path that leads to the workspace. These characters are not legal characters in Linux and Windows pathnames.
User names that are synchronized from an LDAP directory are not case sensitive when users log in to the Filr system.
Local user accounts (user accounts that are created in Filr and not synchronized from an LDAP directory) are case sensitive. Login credentials for local user accounts are stored in the MySQL database.
If both Allow Guest Access and Disable Web Access are selected on the Web Application page of the Administration Console, then Enter as Guest is displayed on the initial Web Access Login dialog and Guest users can see publicly available files and folders. If you choose to disable the web access, you should ensure that the guest access is not enabled.
If a user with administrator privileges chooses to upload image that has to be used in the site branding to Filr, the image fails to upload.To upload site branding image to Filr, you must login as the built-in Filr administrator (admin).
Filr doesn’t support Microsoft’s Access Based Enumeration (ABE) when the backend Windows server uses the Distributed File System (DFS) namespace.
If you have a remote DFS junction on an OES 2015 server that is running NSS for AD, you must ensure that the Refresh Cached Rights interval under Net Folder Settings in the Filr administration console is not set to 0 minutes (meaning that it’s disabled). Otherwise, Filr users will not be able to access files and folders under the DFS target through Filr and the owner of all the files and folders under the target will be displayed as File Sync Agent in Filr.
When the Filr server encounters issue accessing data on a DFS junction in an OES cluster environment, the following error displays:
ConvertXplatErrToFAMTErr xplat status: 0xc7e90503
To fix this problem, ensure that the VLDB service is up and running. For more information about the VLDB service, see OES Documentation.
Unable to Log Into Filr as a Guest User When Filr is Fronted by Access Manager
Unable to Edit a File Using the Edit-in-Place Functionality When Filr is Fronted by Access Manager
Logout Does Not Happen When Filr Is Accessed Directly and Is Fronted by Access Manager
Cannot Use Multiple Identity Injection Policies Simultaneously
Currently, you cannot use a guest user account to log into Filr that is fronted by Access Manager.
If you attempt to edit a file using the edit-in-place functionality when Filr is fronted by Access Manager, the file fails to open.
To workaround this issue, do the following:
Log in to the Access Manager server.
Navigate to Devices > Access Gateways > [Name of the Access Gateway Server] > Edit > Advanced Options.
Set the advanced option NAGGlobalOptions AllowMSWebDavMiniRedir to on.
To apply your changes, click Devices > Access Gateways, then click Update All.
When Filr is fronted by NetIQ Access Manager, only the Filr administrator is able to access Filr directly. When Filr is accessed directly in this configuration, simultaneous logout for the Filr system is not successful.
After the Filr administrator logs in directly to Filr (and Filr is configured with Access Manager), all browser sessions should be immediately closed to ensure logout.
After using the registration link for self-provisioning your user account on the Filr server that is fronted by Access Manager, clicking the same confirmation link again directs you the Filr login page instead of NAM login page.
When NetIQ Access Manager is configured to front Filr, you cannot use multiple identity injection policies simultaneously.