Name | Description |
---|
Username Prefix | This prefix will be prepended to the username before an Active Directory bind is attempted for authentication. |
Username Suffix | This suffix will be appended to the username before an Active Directory bind is attempted for authentication. |
Automatic Suffix | If this option is checked, and the suffix is left blank, then the suffix will automatically be assigned a value of "@<domain>". |
User Search Base | The base folder to search for users under, such as: DC=MyCompany,DC=com The entire subtree under this folder will be searched using the User Search Filter. Multiple subtrees can be specified by putting them in parenthesis, like so: (OU=Administrators,DC=MyCompany,DC=com)(OU=Operators,DC=MyCompany,DC=com) |
User Search Filter | The LDAP search filter that will be used to find a specific user. Use the placeholder {0} as a standin for the login name. |
User List Filter | The LDAP search filter used when querying for the list of all users. Should restrict the type to user. |
User Name Attribute | The attribute on the User object to define the username. |
User Role Attribute | Attributes of this name on the User object will define the user's roles. |
Role Name Attribute | The attribute of this name on the Role object will define the role's name. Leave blank to use the raw value of the attribute defined by the User Role Attribute property. |
Full Name Attribute | The attribute on the User object to define the full name of the user. |
Phone Attribute | The attribute name on the user object that represents the user's phone number. |
Email Attribute | The attribute name on the user object that represents the user's email address. |
SMS Attribute | The attribute name on the user object that represents the phone number that this user receives text messages on. |
Read Timeout | The read timeout in milliseconds for LDAP operations. |
Results Page Size | The number of entries returned per page of results in a query. |
Role Search Base | The base folder to search for roles under, such as: OU=Roles,DC=MyCompany,DC=com The entire subtree under this folder will be searched using the Role Search Filter. If you specify the root of your tree structure, the search may take a very long time. Multiple subtrees can be specified by putting them in parenthesis, like so: (OU=Builtin,DC=MyCompany,DC=com)(OU=Users,DC=MyCompany,DC=com) If you leave this blank the whole subtree of the domain controller will be searched. |
Role Search Filter | The LDAP search filter that will be used to locate roles. |
Allow Anonymous | Determines whether the Gateway will accept blank usernames and passwords for authentication. Note that this check takes place on the Gateway, prior to handing off any credentials to the AD server. If Security Authentication is set to None, then this property should be enabled, otherwise, blank passwords will be rejected by the Gateway. If true, authentication attempts with blank passwords will be passed through to LDAP, which may choose to accept them. |
Use SSL | Works in conjunctions with the Domain Controller Host and Domain Controller Port properties in the Active Directory Properties section. Disable to use "ldap://" protocol, enable to use "ldaps://" |
Security Protocol | Specifies the security protocol between the Gateway and AD server. The following options are available: AUTO: No security protocol is explicitly used or requested by the Gateway. SSL: SSL should be used for the connection. |
Security Authentication | This property specifies how usernames and passwords are used to bind to LDAP. The following options are available: AUTO: Unspecified from the Gateway side, meaning the LDAP implementation will choose. NONE: Anonymous access. SIMPLE: Plaintext username and passwords will be used. STRONG: Usernames and passwords will be encrypted.
The following feature is new in Ignition version 8.0.10
Click here to check out the other new features
SASL: Simple Authentication and Security Layer. See the SASL Properties table below for additional SASL authentication configuration settings. |