Replaceable parameters are entered by using the following syntax: % attributeName%. You must use a replaceable parameter in the Relative path field. In the Relative path field, specify the path that points to user home directories on the selected server. For information about how to create a Net Folder Server, see Section 8.3, Configuring and Managing Net Folder Servers. If you have not already created Net Folder Servers, or if you need to create a new one, click Create Net Folder Server. In the Net Folder Server field, select the Net Folder Server that will be used with the Home directory Net Folders that will be created automatically when a user logs in. Select this option to specify the Net Folder Server and path where user Home directory information is located. For example, the mail LDAP attribute on User objects could be used to enable Filr users to log in to the Filr site by using their email addresses. In addition to the attributes already mentioned in this section, other LDAP attributes can be used for the Filr account name attribute, as long as the attribute is unique for each User object. Then set up a separate source to the same LDAP server and use sAMAccountName as the Filr account name attribute. For example, set up one LDAP source and use cn as the Filr account name attribute. In some cases where not all users are imported successfully, you might need to set up two LDAP sources pointing to the same LDAP server and have each source use a different value for the LDAP Attribute Used for Filr Name. You might need to consult with your directory administrator in order to determine which attribute is best to use. Other LDAP directories might use the uid (unique ID) attribute, depending on the structure and configuration of the directory tree. A more sure alternative for Active Directory is to use the sAMAccountName attribute. Both eDirectory and Active Directory might use the cn (common name) attribute. LDAP directories differ in the LDAP attribute used to identify a User object. The value of this attribute must be unique.ĭuring Filr login, Filr uses this attribute to locate the user in the LDAP directory and then tries to authenticate as that user. Used as the Filr user name when the user is first provisioned from LDAP. For example, the cn attribute cannot be used because it is not a binary attribute. Before you do this, ensure that the attribute that you use is a binary attribute. If you want to map users to a different attribute, select Other in the drop-down list, specify the name of the LDAP attribute, then click OK. If William changes his name to Bill, and you make that change in the LDAP directory, Filr creates a new user named Bill Jones. If this attribute is not set and you rename or move a user in the LDAP directory, Filr assumes that the new name (or the new location of the same name) represents a new user, not a modified user, and creates a new Filr user.įor example, suppose you have a Filr user named William Jones. It ensures that Filr modifies the existing user instead of creating a new user when the user is renamed or moved in the LDAP directory. This attribute always has a unique value that does not change when you rename or move a user in the LDAP directory. For Active Directory, this value is objectGUID. Depending on the directory type that you chose, this field is populated with the name of the LDAP attribute that uniquely identifies a user or group.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |