Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


These instructions assume that you have an in-house installation of Live Forms frevvo up and running. Refer to Configuring the LDAP Security Manager LDAP(s) for Cloud tenants if you have signed up for an LDAP tenant on the cloud server.


  • Contact the frevvo Customer Success team to schedule your Security Manager configuration.
  • frevvo Best Practice recommends that you create a user account in your Active Directory that will house all of your deployed Production forms/flows. This user can be named anything i.e.frevvoProduction but it must be a member of the frevvo.Designer group
  • If you want to preserve Applications/Forms/Flows developed in your trial/starter tenant to your desktop, perform these steps BEFORE changing the Security Manager. :
    1. Download the Applications/Forms/Flows that you want to preserve to your desktop as a backup. Do this for all
      user accounts that have Applications/Forms/flows that you want to keep.
    2. When the backup of all Applications/Forms/flows is completed, delete the user accounts in your Default Security Manager tenant.
  • There are two additional roles in
    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 Administrator Best Practices 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 frevvo Best Practice eliminates the need for this role.

and LDAP/Active Directory 

users and groups can be maintained externally in systems such as Active Directory or Open LDAP.  Follow these steps to integrate 
 and your LDAP server:


In all cases, follow these steps to configure LDAP. These instructions assume that you have an in-house installation of Live Forms frevvo up and running or you have signed up for an LDAP tenant on the cloud server.


    1. Login to 
      as an  administrator (user:admin and password:admin if you have not changed it)
    2. Click on Manage and then Manage Tenants
    3. 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
    4. Click on the plus icon to add a new tenant.
    5. Configure the new tenant - Choose LDAP Security Manager.from the Security Manager Class drop down.
titleAdd New Tenant Screen

Add New Tenant

titleEdit Existing Tenant Screen

      1. 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.


        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 ignore or follow referrals.

        Setting the java.naming.referral property to a value of "ignore" in the Name/Value table configures

        to ignore referrals. Consult your LDAP Administrator for the details.

      2. If you are creating a new tenant:
        1. Enter a tenant id, a tenant name and description.
        2. The Max Concurrent Users is the maximum allowed by your license or less.
        3. 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 admin and can be used to access tenant administrative functions if you cannot log in as an authenticated LDAP tenant admin.
          1. The tenant admin id, password and email fields are required. The Change password on next login is optional. It is checked by default.
        4. Click Submit. You will see your new tenant in the tenant list if the connection to your LDAP server is successful.


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

flows 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

Refer to FAQ - Live Forms frevvo and LDAP for more troubleshooting information.


 A Tenant admin can login directly to Live Forms 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 Live Forms frevvo. If you experience an issue with your LDAP configuration such that you can't login as an Active Directory authenticated user, use this account to login to your tenant as a tenant admin in order to fix your configuration issue. The built-in admin is able to access the

tenant admin functions if your LDAP Server should become inaccessible. Only one built-in tenant admin account is supported.



Self signed certificates are not supported for Live Forms frevvo Online. Although they are supported for

in-house, use of self-signed certificates is not recommended.


These are the properties used to configure the LDAP/Active Directory security manager. The properties in bold are required.

Property DescriptionActive Directory Sample ConfigurationOpenLDAP Sample Configuration
Connection URLldap server url


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]


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]
Connection PasswordPassword for the Connection user.[user password][user password]
Users Base

Searches for users will start from the ldap node specified by this property.I

f 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 checkboxNotifications are emails sent by frevvo to workflows participants. If checked, notifications will be sent.Check the Notifications checkboxCheck 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.

User Member Of1Attribute on a user object storing the groups the user is a member of. memberOf" "
Group Member1Attribute on a group object storing the users that are a member of this group.memberuniqueMember
First Name

Name of the user ''first name'' attribute

Last NameName of the user ''last name'' attribute.snsn

Name of the user ''email'' attribute in the LDAP server.

This value can be used in a rule is used in email notifications


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 data available in


Ignore Case checkbox

If checked, 

ignores the case stored in LDAP systems.

This is primarily for the purpose of determining roles.

Check the Ignore Case checkboxCheck the Ignore Case checkbox
CustomThis is a a comma separated list of attribute names to be retrieved from the LDAP Server.Ex: carLicense,employeeNumberEx: carLicense,employeeNumber

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
  1. If your AD has nested groups, please see this FAQ: How do I enable frevvo to retrieve users from nested groups?

Options for Authentication


Option 1 -


frevvo login page authenticating against LDAP

This is the case where the user will authenticate through the 

'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
's login page:



The basic deployment is IIS fronting 

 and the authentication is done against LDAP.  For that to work you need to:

  1. Install Live Formsfrevvo 
  2. Configure Live Forms frevvo to work with IIS
  3. Configure Windows Authentication 
    1. Configure Windows Authentication on IIS7
    2. Configure Windows Authentication on IIS6
  4. 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 


No additional configuration is needed.


Configure URL Properties in for LDAP SSO

This parameter is needed in frevvo.xml Add the frevvo.internal.baseurl and the frevvo.forms.server.external.url properties to the 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 when using LDAP SSO.  LetLet'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 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 

 server. Follow these steps:


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 this server.

Follow these steps:

  • edit <frevvo-home>/tomcat/conf/
  • Add the properties shown below with your information: Save the changes to the file.

Code Block
Parameter name="frevvo.internal.baseurl" value="http:// <ip or server name of the m/cmachine where the frevvo server is hosted>:<port>" override="false"/>



Control Behavior

If your system is configured for LDAP SSO, the upload and video controls exhibit control exhibits the following behaviors:

  • The "uploading...." snake image displays continuously when uploading an image to an upload control in a form, accessed from a space, on a mobile device.The video control will ask for credentials again in use/design mode in some browsers. Enter your credentials or run the add-on to proceed.

To workaround this issue, configure IIS so that it does not require re-authentication for every single request.