This setting will only be used by mechanisms which support it. A blank value will leave this setting unspecified. (Default is DIGEST-MD5 CRAM-MD5.)Ī realm defines the namespace from which the user is selected. The LDAP provider will use the first mechanism for which it finds an implementation. The attribute name on the user object that represents the phone number that this user receives text messages on.Īn ordered list of space-separated mechanism names. The attribute name on the user object that represents the user's email address. The attribute name on the user object that represents the user's phone number. The attribute on the User object to define the full name of the user. Leave blank to use the raw value of the attribute defined by the User Role Attribute property. The attribute of this name on the Role object will define the role's name. The attribute on the User object to define the username.Īttributes of this name on the User object will define the user's roles. The LDAP search filter used when querying for the list of all users. Use the placeholder as a standin for the login name. The LDAP search filter that will be used to find a specific user. (OU=Administrators,DC=M圜ompany,DC=com)(OU=Operators,DC=M圜ompany,DC=com) Multiple subtrees can be specified by putting them in parenthesis, like so: The entire subtree under this folder will be searched using the User Search Filter. The base folder to search for users under, such as: If this option is checked, the username prefix and suffix will be applied to the Gateway username before a bind is attempted. The following feature is new in Ignition version 8.1.24Ĭlick here to check out the other new features
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |