| Section |
|---|
| Column |
|---|
It is assumed that you have an in-house installation of up and running or you have requested an LDAP tenant in the cloud from frevvo customer support. | Info |
|---|
Safari browsers later than v5.1.7 running on Windows is no longer supported. Issues were found when using Safari with LDAP - SSO. |
|
|
...
| Info |
|---|
If you are a new in-house LDAP customer, use the Add Tenant screen to configure the LDAP tenant. If you are an existing LDAP customer, the migration process copies any existing LDAP configuration from the frevvo.xml or config properties files to the tenant. Once migrated, updating frevvo.xml has no effect on the tenant configuration. Make changes using the Edit Tenant screen. |
...
| Expand |
|---|
| title | Click here for a list of properties and to see which ones are required: |
|---|
|
These are the properties used to configure the LDAP/Active Directory security manager. The properties in bold are required. LDAP Configuration PropertiesThese are the properties used to configure the LDAP/Active Directory security manager. The properties in bold are required. | Property | Description |
|---|
| Connection URL | ldap server url | | Connection User | User to connect to LDAP. This user must have the proper permissions to read and run queries in the ldap server. If using Active Directory, it is common to specify the domain. For instance, TEST\Administrator refers to the user Administrator in the TEST domain. | | Connection Password | Password for the user defined in com.frevvo.security.ldap.connection.name. | | Users Base | Searches for users will start from the ldap node specified by this property.If the value is empty the searches will start from the root domain. | | Groups Base | Searches for the groups will start from the ldap node specified by this property. If the value is empty, searches will start from the root domain | UserId Display
| User attribute that will be visible in frevvo. This is what will be displayed in the list of users a tenant admin sees and has to be unique in the server. Another restriction is that the values for the attribute configured here cannot have spaces. For instance, don't configure CN as the value since it can contain spaces in most systems. | | GroupId Display | Group attribute that will be visible in frevvo. This is, for instance, what will be displayed in the list of groups a tenant admin sees or the groups used in workflows. This attribute has to be unique in the server. | | Notify checkbox | Notifications are emails sent by frevvo to workflows participants. If checked, notifications will be sent. | | All Groups Filter | The expected value is an LDAP filter expression. The expression should return the groups that will be available to be used in frevvo workflows. com.frevvo.security.ldap.groupIdDisplayAttribute | | All Users Filter | The expected value is an LDAP filter expression. The expression should return the users that will be available to be used in frevvo work flows and authentication. com.frevvo.security.ldap.groupIdDisplayAttribute | | User Member Of | Attribute on a user object storing the groups the user is a member of. | | Group Member | Attribute on a group object storing the users that are a member of this group. | | First Name | Name of the user ''first name'' attribute | | Last Name | Name of the user ''last name'' attribute. | Email
| Name of the user ''email'' attribute in the LDAP server. This value can be used in a rule is used in email notifications | | Manager | Attribute on a user object storing the DN of the user’s manager. This value can be retrieved in a rule or used in flow navigation using the subject.reports.to data available in . | | Ignore Case checkbox | If checked, ignores the case stored in LDAP systems, primarily for the purpose of determining roles. | | Custom | This is a a comma separated list of attribute names to be retrieved from the LDAP Server. | | TLS | This enables simple authentication over TLS. If checked, a trusted certificate for the LDAP server is required. |
|
...
The first issue occurs when the user logs in. For instance, John Stevens LDAP account is JStevens but he logs in as jstevens, he will be recognized by case insensitive LDAP and thus granted access but will not be recognized as a designer or as a tenant admin by . To solve this, check the Ignore Case checkbox on the LDAP Configuration screen. To prevent issues you could always login to using lower case jstevens. LDAP will grant access as it is case insensitive and will know that you may have the designer or admin special permission. However users can forget to do this. Setting Ignore Case in your LDAP security configuration will solve this.
The second problem is in directing tasks to users if your LDAP user names are mixed case. One solution is to use hidden controls on your forms with rules to convert the case of user names to lower case. The example below shows two text controls on a form, one visible, EmployeeMixedCase, and the other hidden, Employee.
...