...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
| Section | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Required: Active Directory Customers using LDAP must ensure frevvo.TenantAdmin and frevvo.Designer groups are specified on your LDAP/AD server. The group names must be spelled as shown. Upper/lower case may be a factor for Open LDAP systems.
- Tenant admin users must be assigned to the frevvo.TenantAdmin group.
- Designer users must be assigned to the frevvo.Designer group. Note that, unlike the default security manager, users in the frevvo.TenantAdmin group must also be in the frevvo.Designer group to design forms/workflows.
Optional: There are two additional roles in frevvo - frevvo.Publisher and frevvo.ReadOnly. These roles are optional.
- In order to give a user the frevvo.publishers role, create the frevvo.Publisher group in your AD and assign users to it. Refer to the Publisher Role Documentation for an explanation of this role.
- In order to give a user the frevvo.ReadOnly role, create the frevvo.ReadOnly group in your AD and assign users to it. Following frevvoBest Practice eliminates the need for this role.
| Warning |
|---|
|
Configuring frevvo and LDAP/Active Directory
users frevvo users and groups can be maintained externally in systems such as Active Directory or Open LDAP. Follow these steps to integrate and integrate frevvo and your LDAP server:
- Collect the key information listed below and verify the Prerequisite Tasks have been performed.
- Create a tenant with the LDAP/Active Directory Security Manager class.
- Once you have your tenant successfully connecting with your LDAP server, review the available options regarding the authentication process.
...
- LDAP server name or ip
- LDAP server port
- User name and password with proper permissions to access and browse LDAP.
- LDAP groups and/or users that will be considered frevvo designers. These users will be able to create forms and flows in frevvo.
- LDAP groups and users that will be considered administratorsfrevvo administrators.
- LDAP groups and users that will be considered publishersfrevvo publishers. This role gives a user the permission to go to the home page of every other tenant user.
- LDAP groups and users that will be considered ReadOnly.
- LDAP user and groups base filters
- LDAP all users and all groups filters
LDAP the attribute names in your Active Directory for UserId Display, GroupId Display, User Member Of, Group Member, First Name, Last Name, Email and Manager (optional)
...
The connection to your LDAP server is configured at the tenant level.
- New in frevvo in-house customers can add an LDAP tenant and configure the LDAP parameters via the Add Tenant screen. LDAP properties can be updated at anytime via the Edit Tenant screen.
- Cloud customers must request an LDAP tenant from frevvo customer support. Cloud customers will receive a default tenant login from frevvo and then they can edit the LDAP configuration properties using the Edit Tenant screen to connect to their LDAP server.
...
In-house customers:
- Login to as frevvo as an administrator (user:admin and password:admin if you have not changed it)
- Click on Manage and then Manage Tenants
- You will see a page where the current tenants are listed. If this is a new installation you will only see the default tenant d
- Click on the
plus icon to add a new tenant.
- Configure the new tenant - Choose LDAP/Active Directory Security Manager from the Security Manager Class drop down.
| Panel | ||
|---|---|---|
| ||
 |
| Expand | |||||
|---|---|---|---|---|---|
| |||||
|
Enter your LDAP Configuration Properties and Sample Configurations. Alternatively, you can start off from one of the sample configurations and provide only the key information listed above. See below for information on the TLS checkbox.
Note The Name/value table highlighted in the image allows you to configure up to 10 additional LDAP properties. See this Oracle website for a complete list of all available LDAP properties. For example, you can configure to frevvo to ignore or follow referrals.
Setting the java.naming.referral property to a value of "ignore" in the Name/Value table configures to frevvo to ignore referrals. Consult your LDAP Administrator for the details.
- If you are creating a new tenant:
- Enter a tenant id, a tenant name and description.
- The Max Concurrent Users is the maximum allowed by your license or less.
- Specify the User ID, password and email address of a user that will have the tenant admin permission. This user id is the built-in and can be used to access tenant administrative functions if you cannot log in as an authenticated LDAP tenant admin.
- The tenant admin id, password and email fields are required. The Change password on next login is optional. It is checked by default.
- Click Submit. You will see your new tenant in the tenant list if the connection to your LDAP server is successful.
| Warning |
|---|
The Ignore Case and Notify checkboxes are checked by default. It is recommended that you leave them checked. Refer to Mixed or Upper case User Names topic for an explanation of the Ignore Case option. The Notify checkbox determines whether the task notification emails setup in frevvo workflows are sent or not. |
Clicking the submit button tests the connection. Any errors are displayed at the top of the form. Here is an example of an error when there is a typo in the LDAP server name:
Here is another example if the connection password is not correct
...
Here are some quick tests to check if the LDAP configuration is correct:
- Login as the tenant frevvo tenant admin for the LDAP tenant.
- Click on the Manage Users link.
- Click All. You should see a list of LDAP users which were assigned one of these roles frevvo roles on the LDAP server: frevvo.TenantAdmin, frevvo.Designer, frevvo.Publisher, frevvo.ReadOnly
- Now, click Back To Manage Tenant.
- Click Manage Roles. You should see a list of groups from your LDAP server.
- Log out from from frevvo (you should be currently logged in as the tenantadmin)
- Try to login with the user name and password of a user in LDAP. You need to specify the proper tenant when logging in. For instance, if john is a valid LDAP user and the name of the LDAP tenant is MYLDAP, you should log in as john@MYLDAP. The password would be john's password in LDAP.
Since you are using LDAP to define users frevvo users and roles (i.e., groups), you do not see an Add User icon or Add Role icon on the Manage Users or Manage Roles pages.
LDAP Built-in Admin
A Tenant admin can login directly to frevvo or login with a user id who has been given tenant admin permissions in your Active Directory.
When you create a new tenant you are prompted to set up a tenant admin user id, password and email address. This tenant admin does not authenticate via your LDAP IDP. It only exists in frevvo. If you experience an issue with your LDAP configuration such that you can't login as an Active Directory authenticated user, use the built-in admin to login to your tenant as a tenant admin in order to fix your configuration issue. The built-in is able to access the tenant frevvo tenant admin functions if your LDAP Server should become inaccessible. Only one built-in tenant admin account is supported.
Browse this URL to login as the built-in: <base_URL>/frevvo/web/admin/login. When specified, will frevvo will prepend the base URL to the URLs in your Form/Document Actions. The <base_URL> is typically http(s)://<your servername>:<port>.
...
- Login as your authenticated LDAP tenant admin. Click the Edit Tenant link. The Admin User information is displayed .
- If logging in as the authenticated LDAP tenant admin is not possible, browse this admin specific URL - <base-url>/frevvo/web/admin/login. Enter the built-in userid. Click Forgot Password? Once you have changed the password, browse the admin specific URL again and login with the tenant admin user id and the new password. If you need to change the password again, or make changes to your tenant, click the Edit Tenant link. The built-in password can be changed on this screen.
This error message displays if any other user clicks on the Forgot Password? link after browsing the admin specific URL:
What if you do not remember the userid of your original tenant admin? Follow these steps:
- Login as your authenticated LDAP tenant admin. Click the Edit Tenant link. The Admin User information is displayed .
- If logging in as the authenticated LDAP tenant admin is not possible, the frevvo (Cloud customers) and in-house superuser can see the built-in tenant userid from the Edit Tenant page.
Secure LDAP Configuration
will frevvo will be connecting to your LDAP server over the network. Here are two methods to secure the LDAP connection:
...
| Note |
|---|
Self signed certificates are not supported for frevvo Online. Although they are supported for in frevvo in-house, use of self-signed certificates is not recommended. |
Finally you need to install your signed or self-signed certificate. You can import the certificate into a keystore that can that frevvo can access and trust. Follow the instructions for your keystore. If is If frevvo is installed in a tomcat server, the tomcat keystore can be used. Refer to this Apache Tomcat website for instructions.
...
| Property | Description | Active Directory Sample Configuration | OpenLDAP Sample Configuration |
|---|---|---|---|
| Connection URL | ldap server url | In-house ldap://[your server]:[port, typically the default is 389 ] Cloud - SSL installed on your LDAP server ldaps://[your server]:[port, typically the default is 636] | In-house ldap://[your server]:[port, typically the default is 389] Cloud -SSL installed on your LDAP server ldaps://[your server]:[port, typically the default is 636] |
| 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. Ex: an entry of TEST\Administrator refers to the user Administrator in the TEST domain. | [user name] | cn=admin,dc=test,dc=frevvo,dc=com |
| Connection Password | Password for the Connection user. | [user password] | [user password] |
| 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. | CN=Users,DC=test,DC=windows,DC=frevvo,DC=com | DC=test,DC=frevvo,DC=com |
| 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 | CN=Users,DC=test,DC=windows,DC=frevvo,DC=com | DC=test,DC=frevvo,DC=com |
| 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. | sAMAccountName | uid |
| 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. | sAMAccountName | entryDN |
| Notify checkbox | Notifications are emails sent by frevvo to workflows participants. If checked, notifications will be sent. | Check the Notifications checkbox | Check the Notifications checkbox |
| All Groups Filter | The expected value is an LDAP filter expression. The expression should return the groups that will have access to frevvo forms and workflows. | (objectClass=group) | ( | (objectClass=groupOfUniqueNames)(objectClass=organizationalRole)) |
| All Users Filter | The expected value is an LDAP filter expression. The expression should return the users that will have access to frevvo forms and work flows. | (objectClass=user) | (objectClass=person) |
| User Member Of1 | Attribute on a user object storing the groups the user is a member of. | memberOf | " " |
| Group Member1 | Attribute on a group object storing the users that are a member of this group. | member | uniqueMember |
| First Name | Name of the user ''first name'' attribute | givenName | cn |
| Last Name | Name of the user ''last name'' attribute. | sn | sn |
| 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. It can also be used in flow navigation using the subject.reports.to data available in frevvo. | manager | manager |
| Ignore Case checkbox | If checked, ignores frevvo ignores the case stored in LDAP systems. This is primarily for the purpose of determining roles. | Check the Ignore Case checkbox | Check the Ignore Case checkbox |
| Custom | This is a a comma-separated list of attribute names to be retrieved from the LDAP Server. | Ex: carLicense,employeeNumber | Ex: carLicense,employeeNumber |
| TLS | This enables simple authentication over TLS. If checked, a trusted certificate for the LDAP server is required. Refer to the secure the connection topic for details. | Check if you are using TLS to secure the connection. | Check if you are using TLS to secure the connection |
...
- Options 1: Users can login using the login frevvo login page and will frevvo will delegate authentication back to the LDAP/Active Directory server. See the example below. There is nothing more to do if you choose this option.
- Options 2: You can implement Single Sign On with IIS. See the details below.
...
This is the case where the user will authenticate through the frevvo's login page but delegate authentication to LDAP. Lets assume that your tenant named 'LDAP' was successfully configured to connect to your LDAP server and there is a user 'john' in your LDAP server. You can now login directly via frevvo's login page:
The password provided in the login page is the user's password in LDAP. A very important point to note is that the user name, "john" in the example above, needs to match the value for the LDAP entry attribute configured in the property UserID Display field on the Edit Tenant screen. For instance, for Active Directory, the value of this property is normally sAMAccountName. That means will means frevvo will try to find an entry in LDAP that has sAMAccountName=john.
...
In this scenario, a user authenticates to his windows account and tries to use frevvo. Since the user is already authenticated to the network, will frevvo will recognize his credentials and automatically forward the user to his accounthis frevvo account, if he is a designer, or allow the user to use a form/flow if those resources are available to the tenant.
The basic deployment is IIS fronting and fronting frevvo and the authentication is done against LDAP. For that to work you need to:
- Install frevvo
- Configure frevvo to work with IIS
- Configure Windows Authentication
- In IIS, Make sure that Anonymous Authentication or Basic Authentication is NOT configured in the Web Application (Default Web) that will be used to proxy requests to frevvo.
Please also refer to the force auth property for forms and flows. Force auth lets you override SSO for an individual form or flow.
| Info |
|---|
If you are using LDAP and SSO, and you want to embed the in frevvo in your website, refer to Embedding the Task List for important information. |
...
Signing in from within the network
In this case, the server the frevvo server and the Active Directory server are running on the same network. The user is already authenticated to the windows network and points the browser to:
...
The user will automatically authenticate to frevvo. It is crucial that the LDAP user is known to frevvo, in other words, the user should be one of the entries retrieved by the LDAP expression configured in the All Users Filter on the LDAP configuration screen.
Signing in from outside the network
In this case, the server the frevvo server and the Active Directory server are running on different networks. The user is trying to hit the URL below from outside the network.
...
Since the user is not authenticated in the windows Network, he will be prompted by the browser for credentials. IIS will authenticate the user in the network and forward the request to frevvo. The user will be automatically redirected to his initial page without having to re-enter his credentials.
...
Add the frevvo.internal.baseurl and the frevvo.forms.server.external.url properties to the frevvo-config.properties when using LDAP SSO. The frevvo.internal.baseurl property is needed for for various activities like accessing the ACL page, publishing templates, resetting tasks etc. Let's say you have a browser signed in via SSO to machine m1 (port 80). IIS is running on m1 (port 80) redirecting /frevvo/web to frevvo running on m2:8082. The browser submits a form to m1, IIS redirects to m2:8082. The doc action is a frevvo:// URI which gets resolved to http://m1/frevvo/... POSTs frevvo POSTs to this URI but m1 rejects the POST since it is not authenticated.
To avoid situations such as these, set the frevvo.internal.baseurl to the actual host:port of the serverthe frevvo server.
If the frevvo.forms.server.external.url property is set, all share dialogs for forms and flows will use this as the external URL. This may be needed when using frevvo.forms.server.external.url if that external url is not also accessible from the form server machine. Use the syntax shown in the example. change the <myexternalhost>and <port> to your external server name and the port that you are using for on for frevvo on this server.
Follow these steps:
...
Mixed or Uppercase User Names
| Info |
|---|
frevvo user names are case sensitive; the user name johndoe'' is not the same as JohnDoe. Several LDAP systems are case insensitive. Thus the two user names would resolve to the same LDAP account but to different frevvo user accounts. To avoid case issues follow these steps described in more detail below:
|
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 frevvo. To solve this, check the Ignore Case checkbox on the LDAP Configuration screen. To prevent issues you could always login to frevvo using lower case jstevens. LDAP will grant access as it is case insensitive and frevvo 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 frevvo 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.
...
LDAP administrators can configure to frevvo to ignore or follow referrals by entering the LDAP property name and value in the table provided on the Add Tenant (on-premise) or Edit Tenant (cloud) screens.
...