Live Forms v5.3 is no longer supported. Click here for information about upgrading to our latest GA Release.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 45 Next »

It is possible to create user and groups in frevvo 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. frevvo can leverage your existing users repository.

 There are two configuration scenarios when integrating frevvo with LDAP. Each one uses a different Security Manager.

  1. frevvo integrates with an external LDAP/AD system and is in full control of user authentications. Use the LDAP Security Manager in this situation. Click here for the configuration details.

  2. frevvo 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, frevvo 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. Click here for the configuration details.

On This Page:

Retrieving Custom Attributes from the LDAP Server 

Active directory attributes can be retrieved from the LDAP server using Business Rules. The rules use the frevvo the _data.getParameter syntax to populate form controls with the Active Directory information. There are many attributes available in Active Directory. View  this website for a partial list. Multi value attributes are also supported. This feature works if you are using an LDAP or LDAP Container Security Manager configuration.

Configure Retrievable Attributes 

Single-value Attributes

frevvo will automatically pull the logged in user's First Name, Last Name, Email from Active Directory. The designer can use built-in methods in a rule to populate controls on a form. For example, the business rule shown fills the respective form fields with the First/Last Names and Email Address of the logged in user.


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 attribute names to be retrieved. Let's use the employee's Middle Initials and Home Phone as an example. The attributes for Middle Initials 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.  
 <Parameter name="" value="initials,telephoneNumber," override="false"/> 

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

Add the additional lines to the business rule to populate the Middle Initials and Home Phone fields. 


The image shows a simple form using the rule above to pull the Employee's First Name, Middle Initial, Last Name, Home Phone and Email Address from Active Directory on the LDAP server.

Multi-valued 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 those options. 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.  

 <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 frevvo rule. This rule will populate the options of a dropdown control named carLicense.


  • No labels