Versions Compared


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

It is possible to create user and groups in

and use them to control access to the system as well as create workflows. It is also common that the list of users and groups is maintained externally in systems such as Active Directory or Open LDAP.
 can leverage your existing users repository.

There are two configuration scenarios when integrating

with LDAP. Each one uses a different Security Manager.

  1. Frevvoproduct
    integrates with an external LDAP/AD system and is in full control of user authentications. Use the LDAP Security Manager in this situation.

  2. Frevvoproduct
    is deployed to an existing servlet container that is already handling user authentications through LDAP. Authentication, in this case, is the responsibility of the container. However,
    is responsible for runtime authorization and design time querying of user metadata. Use the LDAP Container Security Manager
    in this situation as that reuses the existing LDAP connector but relies on the container for user authentications. 


On This Page:

Table of Contents

Retrieving Custom Attributes from the LDAP Server

When a user is successfully authenticated by the LDAP security manager,

 retrieves the following basic user information from the LDAP server: 

Last Name
First Name
Email address 

Using a business rule, you can populate controls in your form with this information. 


There are many attributes available in Active Directory. View this website for a partial list. Single and multi-value attributes are supported. Active Directory custom attributes can be retrieved for users in a 

 tenant using the LDAP Security Manager or the LDAP Container Security Manager.  


You can retrieve additional custom attribute information from the LDAP server using the configuration parameter "" and business rules.   

Configure Retrievable Attributes

Single-value Attributes

If you want to pull additional information from Active Directory into your form, you must add a context parameter to the <frevvo-home>\tomcat\conf\catalina\localhost\frevvo.xml file. The configuration parameter is "" and the value is a comma separated list of custom attribute names to be retrieved. Let's use the employee's Middle Initial and Home Phone as an example. The attributes for Middle Initial and Telephone Number are initials and telephoneNumber respectively. 

Follow these steps to modify the configuration:  

  1. Stop Live Forms if it is running.
  2. Navigate to <frevvo-home>\tomcat\conf\catalina\localhost\frevvo.xml.
  3. Open the file with a text editor.
  4. Add the parameter shown below to the Active Directory or OpenLDAP sections of the file.  
Code Block
 <Parameter name="" value="initials,telephoneNumber," override="false"/> 

     5. Save the file after all your changes are made. Restart 


Write a rule to populate controls in your form with the firstname, lastname, email address plus the additional attributes specified in the configuration parameter. Notice the initials and the telephone number controls in the image are filled with the user information from the LDAP server.

Multi-value Attributes

Attributes with more than one value are also supported. For example, The carLicense attribute can return multiple licenses. You can write a rule to populate dropdown options with the specified car license values. Make sure the carLicense attribute is configured in the frevvo.xml file and of course, there are multiple carLicense attributes, each one containing a different value for the dropdown options, set up for appropriate users on the LDAP server.  

Code Block
 <Parameter name="" value="initials,telephoneNumber,carLicense" override="false"/> 

A JSON array string listing multiple car licenses is returned and it can be used in a 

 rule to populate the options of a dropdown control named carLicense.