| Section | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
LDAP Configuration Properties
These 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. |
Sample Configurations
| Property | Active Directory Sample Configuration | OpenLDAP Sample Configuration |
|---|---|---|
| Connection URL | ldap://[your server]:[port, typically the default is 389 ] | ldap://[your server]:[port, typically the default is 389 ] |
| Connection User | [user name] | cn=admin,dc=test,dc=frevvo,dc=com |
| Connection Password | [user password] | [user password] |
| Users Base | CN=Users,DC=test,DC=windows,DC=frevvo,DC=com | DC=test,DC=frevvo,DC=com |
| Groups Base | CN=Users,DC=test,DC=windows,DC=frevvo,DC=com | DC=test,DC=frevvo,DC=com |
| UserId Display | sAMAccountName | uid |
| GroupId Display | sAMAccountName | entryDN |
| Notify checkbox | Check the Notifications checkbox | |
| All Groups Filter | (objectClass=group) | ( | (objectClass=groupOfUniqueNames)(objectClass=organizationalRole)) |
| All Users Filter | (objectClass=user) | (objectClass=person) |
| Group Member | member | uniqueMember |
| User Member Of | memberOf | " " |
| First Name | givenName | cn |
| Last Name | sn | sn |
| Manager | manager | manager |
| Ignore Cas | Check the Ignore Case checkbox | Check the Ignore Case checkbox |
| Custom | carLicense, employeeName | carLicense |
| TLS | Check to secure the connection using TLS | Check to secure the connection using TLS |
Refer to this documentation for more information and here for some troubleshooting tips.
Configuring the LDAP Container Security Manager
...
Configuring the SAML Security Manager
To successfully create a tenant using the SAML Security manager.You will need the following:
...
- The metadata for your Identity Provider
...
- Attribute mapping information
cloud customers, migrating your trial tenant to the SAML Security Manager, will make the changes via the Edit Tenant screen. Once accessed, follow these steps beginning with step 3.
- Log onto as the superuser (on-premise) or the tenant admin (cloud).
- Access the Add Tenant (on-premise) or Edit Tenant (cloud) screen.
- Select SAML Security Manager from the Security Manager Class dropdown.
- Copy the Service Provider (frevvo) metadata into the Service Provider field. The xml should be pasted without the prolog. For example, the image shows an example of the frevvo metadata file before pasting:
- Retrieve the metadata for your Identity Provider. For example, for the Shiboleth product the metadata is located in the idp-metadata file.
- Paste the IDP metadata into the Identity Provider field. This metadata should also be pasted without the prolog.
- Check the Ignore Case checkbox to prevent case mismatch during authentication. This parameter converts the user provided identifier and the retrieved user identifier/manager user identifier to lowercase.This is recommended especially for especially for customers migrating from using the frevvo security manager with lower case user identifiers to using LDAP which is case insensitive. Refer to the Mixed or Upper case User Names topic for more information if you are using LDAP for authentication.
- requires the IDP to provide attributes that map to the attributes on the tenant screen. The IDP must provide the name for each attribute. For Example, here is an example of the attribute-resolver.xml file in a Shibboleth IDP implementation.
- Paste the name for each attribute in the corresponding field.
- Custom attributes can be retrieved from your Identity provider by typing the attribute names in the Custom field separated by a comma. Refer to this topic which discusses an example that pulls additional attributes from Active Directory into a form using business rules.
- Click Submit.
- Return here to see how to login to your SAML tenant.
...