Prerequisites

Authentication Only mode:

When you create your  SAML tenant, you can select Authentication Only mode..This is done by checking a checkbox when you configure your SAML tenant.

If Authentication Only is selected, SAML is used only for authentication. Authorization depends on the roles defined in .  SAML will authenticate the user but not retrieve any of the attributes.
You may choose to use this mode if you:

• do not want to add  roles to your LDAP.

• LDAP has many roles that have no relevance to your workflow.

• Find the SAML mapping for the other required attributes complex. For example, retrieving the manager user id and role names may require writing custom rules.

In this mode, manual creation of users & roles in the  tenant is required. The  CSV upload feature makes this easy.

If Authentication Only is not selected, users will be added (discovery) at runtime when they log in for the first time. It is important to consider the following points before making your decision.

• User discovery:

  • There is no guarantee that the first login will occur before a task is created for a specific user /role. If you have workflows, that are routed to users who have not logged in yet, your workflow may not do what you expect. If the user’s role changes after 1st login but before the next task is routed to their new role, the task will not appear on their Task List. For example, a user with the role of employee, logs into . The user then gets prompted to manager. The user will not receive a task routed to the user's new role of manager. workflow is initiated before the user logs out and logs in again and the user account is updated.

  • Manually creating/uploading users and roles ahead of time avoids this situation.
    

•  Active Directory:
  • Customers using LDAP must ensure that the frevvo.User, frevvo.TenantAdmin and frevvo.Designer roles are specified on their LDAP/AD server. 
    
    • • All users requiring access to  must be assigned to the frevvo.User group. 
      • Tenant admin users must be assigned to the frevvo.User and frevvo.TenantAdmin groups,
      • Designer users must be assigned to the frevvo.User  and frevvo.Designer groups.
        
        

Configuring the SAML Security Manager

In the directions given below, the Service Provider refers to frevvo . The metadata for your SAML tenant must be obtained first. Customers will need to configure the metadata when creating the SAML tenant.

1. In-house Customers Only
   1. Generate Your Certificate
   2. Install the Java Cryptography Extension API
2. Create the frevvo Metadata file.
3. Configure your Identity Provider
4. Create/edit the SAML tenant
5. Manage Users/Roles for your SAML tenant
6. Logging into Live Forms in a SAML Tenant

Step 1 - In-house Customers Only

Cloud customers can skip the Generate Your Certificate and Install the Java Cryptography steps. These instructions are provided for On-premise customers only.

Generate Your Certificate

If you re using the frevvo tomcat bundle, the supplied keystore, frevvoKeystore.jks is located in the <frevvo-home>/tomcat/lib folder, The keystore contains a default certificate with alias=frevvo and password=p@ssw0rd. Replace this  with a certificate for your installation.

• The alias and password can be configured with the properties, com.frevvo.security.saml.key and com.frevvo.security.saml.password in the <frevvo-home>\tomcat\conf\localhost|frevvo.xml file.

This certificate is used to sign/encrypt the SAML request. The use of a long-lived self-signed certificate is recommended.

Since the keystore is located outside the frevvo war, you can use the Java keytool to generate and store your certificates. Folllow these steps:

1. Login as administrator.

2. Delete the existing certificate:

   keytool -delete -alias frevvo -keypass p@ssw0rd -keystore frevvoKeystore.jks -storepass p@ssw0rd

3. Generate a new certificate: Here is the command: Change the -dname value to the DNS name of your IDP

   keytool -genkey -dname "cn=app.frevvo.com" -alias frevvo -keypass p@ssw0rd -keystore frevvoKeystore.jks -storepass p@ssw0rd -keyalg rsa -keysize 2048 -validity 3650

4. The certificate can be viewed (and used in the metadata XML) by exporting it to a file:
   

   keytool -exportcert -alias frevvo -file frevvo.rfc -rfc -keystore frevvoKeystore.jks -storepass p@ssw0rd

Install the Java Cryptography Extension

The Java Cryptography Extension (JCE) provides a uniform framework for the implementation of security features in Java. These files are needed to avoid an i"llegal key size" error which can happen if these files are missing in the Java Development Kit (JDK) software of your on-premise installation.

Follow these steps to install the JCE files into the JDK:

1. Go to the Oracle Java SE download page. 
2. Scroll down … Under "Additional Resources" section you will find "Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy File"
3. Download the version that matches your installed JVM  - for example, download UnlimitedJCEPolicyJDK8.zip if you are using JDK/JRE version 8
4. Unzip the downloaded zip. 
5. Copy local_policy.jar and US_export_policy.jar to the <JAVA_HOME>/jre/lib/security (Note: these jars are already there so you have to overwrite them)
6. Restart .

Step 2 - Create the Live Forms Metadata file

Follow these steps to generate the frevvo metadata for your SAML tenant. You can do this even if the tenant has not been created yet.

1. Paste this URL into your browsr:

   1. Cloud Customers: https://app.frevvo.com:443/frevvo/web/saml/metadata/alias/{t} - replace {t} with the tenant id of your SAML tenant.

   2. On-premise customers: http://<server>:<port>/frevvo/web/saml/metadata/alias/{t} - replace <server> with the ip of your server, <port> with the port number (if applicable) and t with your tenant id).
      
      

2. When the metadata displays, right click and select the browser option to View the Page source.
   
   
   
   

3. Save the page as an xml file.
4. Metadata must be generated for each SAML tenant. Each tenant will have a unique URL.

Step 3 - Configure Your Identity Provider

1. Configure the Service Provider metadata for your Identity Provider. For example, the Shiboleth Identity provider requires modification of a file to provide the path to the tenant metadata xml file created above.
2. Your Identity Provider must be configured to expose the attributes that requires. Attribute mapping is done when you create the SAML tenant. These are:
   1. User Id
   2. First Name
   3. Last Name
   4. Email
   5. Manager Id (optional)
   6. Groups
   7. Custom Attributes (optional)

We know that your IDP software of choice is outside of the frevvo server software and that you have the expertise in house to install, configure and maintain your IDP software. But here are some tips we have found that may assist you.

Step 4 - Create/edit the SAML tenant

To successfully create a tenant using the SAML Security manager, you will need the following:

  metadata file

• The metadata for your Identity Provider
• Attribute mapping information  

cloud customers, migrating your tenant to the SAML Security Manager, will make the changes via the Edit Tenant screen. Once accessed, follow these steps beginning with step 2.

 Log onto as the superuser (on-premise) or the tenant admin (cloud).

1. Access the Add Tenant (on-premise) or Edit Tenant (cloud) screen.
2. Select SAML Security Manager from the Security Manager Class dropdown.
3. 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:
   
   
   
   
4. Retrieve the metadata for your Identity Provider. For example, for the Shiboleth product the metadata is located in the idp-metadata file.
   
   
5. Paste the metadata into the Identity Provider field. This metadata should also be pasted without the prolog.
   
   
   
   
6. Check the Ignore Case checkbox if you are using LDAP for authentication and you want to ignore the case stored in LDAP systems for users/roles. It is checked by default. Refer to the Mixed or Upper case User Names topic for more information.

7. Check the Authentication Only checkbox if you want SAML to handle authentication and provide user identification but all other user attributes come from the  database.
   
   When checked, the screen display changes as attribute mapping, other than the mapping for the user id and custom attributes, is no longer necessary.
   
   
   
   

   Authentication Only:

   • If Authentication Only is checked:
     • SAML will authenticate the user but not retrieve any of the attributes. Authorization depends on the roles defined in . Changes made in the UI will not be overridden if the user logs out and then logs in again.
       
     • Manual creation of users & roles in the SAML tenant is required. This can be done with a csv upload.
       
       
   • If Authentication Only is unchecked:

     • All users requiring access to must be assigned to the frevvo.User group in Active Directory. Tenant Admins must be assigned to the frevvo.User and frevvo.TenantAdmin groups. Designer users must be assigned to the frevvo.User and frevvo.Designer groups.

     • Users are added (discovered) when they log in. 
     • It is important to know that a SAML tenant in this mode (SAML/LDAP handles authentication and authorization) that users and tenant admins can modify user information in the UI. If user information/role assignment is changed in the UI, the changes will be overwritten by the information in SAML the next time the user logs out and then logs back in again. In this case, make the changes in your Active Directory to make them permanent.
       

8. Map the attributes configured in your Identity Provider by entering the name for each attribute in the corresponding field on the screen. Be sure to provide the attribute name - not the friendly name. For example, if you are using Shibboleth for your Identity Provider the attribute information is located in the attribute-resolver.xml file. The image shows the section of the file where the attributes are defined.
   
   
   The image below shows the attribute mapping on the screen with the attribute names from the Shibboleth file:

   
   
   

   If Authentication Only mode is enabled for your tenant, mapping is only required for the User Id. Refer to step 8 for the details

9. Custom attributes can be mapped by typing the attribute names in the Custom field separated by a comma.
10. Configure a tenant admin account. This account  does not require SAML authentication. This tenant admin can log directly into providing a default security manager backdoor.
    
    1. The tenant admin id, password and email fields are required.
    2. When this tenant admin performs a form based login i.e. /frevvo/web/login, the password entered on this screen is used for authentication. This is also the URL used by the API.
    3. If the tenant based login url is used i.e. /frevvo/web/tn/{t}/login then SAML login is used.
    
    
    
    The forgot password function works for a SAML tenant admin user. For all others, it will display the error message about not being supported for the tenant.
    
    
    
    
11. Configure the Business Calendar for your tenant and HTTP Authorization Credentials if required.
12. Click Submit.
    

Step 5 - Users/Roles in a SAML tenant

Choosing the Authentication only option in your SAML tenant implies that the user and roles will be managed from . You may choose this mode if:

1. 1. You do not want to add  roles to your LDAP.
   1. LDAP has many roles that have no relevance to your workflow.
   2. Find the SAML mapping for the other required attributes complex. For some IDPs, retrieving the manager user id and role names may require writing custom rules.

When Authentication Only is selected (checked) there is no discovery of Users & Roles. They must be created in your tenant manually. The CSV upload is a good way to do this.

When Authentication Only is not selected (unchecked)  will discover new users at run-time. However users are only discovered when the person tries to login. They are not discovered nor is their user data (email, name, report-to) kept in sync automatically. It requires the user to login. So, this does not necessarily remove the need for manually creating/uploading users and roles ahead of time nor does it remove the need to continuously update the users when changes are made in LDAP. 

If you have workflows that are routed to users/roles there is no guarantee that the required users will login before a task is created for that user (specifically or via a role). For example, if  a workflow is routed to a specific user and it is performed before the first login of that user,  will send an email to the tenant admin indicating that the user is unknown. Routing based on the user's manager will fail. Routing based on a role will succeed but the user will receive no notification.

Manually creating/uploading users/roles in  ahead of time avoids this situation. 

Step 6 - Logging into Live Forms in a SAML Tenant

1. Paste this URL into your browser:

   1. Cloud Customers: https://app.frevvo.com:443/frevvo/web/tn/{t}/login - Replace {t} with the name of your SAML tenant.

   2. On-premise Customers:http://<server>:<port>/frevvo/web/tn/{t}/login. Replace <server> and <port> with your server information and t with the name of your SAML tenant.

2. screens display depending on the level of authorization specified for the user. Designer users will see the Application Home Page while non-designer users will be directed to their Task List.

This URL redirects to /web/saml/login/alias/{t}. This initiates the SAML authentication process by redirecting to the Identity Provider login page.  If the user is authenticated, the rest of the standard login processing is done (verify license, redirect on success etc).

Logging into a SAML tenant directly (user@saml tenant name) displays an application error message.

On-premise customers using the tomcat bundle will see the following entry in the  error log:

Application error processing /frevvo/web/login?null java.lang.UnsupportedOperationException: null

SAML Tenant backdoor admin user

Just a reminder that the tenant admin account can login directly into or use the SAML login.

When you create a new tenant you are prompted to set up a tenant admin user id and password. If you are using a SAML IDP, this tenant admin does not authenticate via your SAML IDP. It only exists in . If you experience an issue with your SAML configuration such that you can't login as a SAML authenticated user, this account provides a backdoor you can use to login to your tenant as a tenant admin in order to fix your SAML configuration issue. Only one backdoor tenant admin account is supported.

If your tenant originally used the Default Security Manager and then you changed to the SAML Security Manager, this tenant admin account has already been setup. If you have forgotten the password, you can change it by :

• Using the Forgot Password? feature for the tenant admin account.
• Logging in as a SAML authenticated tenant admin and changing the password via Manage Users.
  

What if you do not remember the userid of your original tenant admin? Follow these steps:

1. Login as your authenticated SAML tenant admin
2. Click Manage Users and click the edit admin icon.

Accessing a Space in a SAML tenant on a mobile device will not display a logout button.

Troubleshooting Tips

Login fails with illegal Key Size Error

After a failed login, ithis error message appears in the <frevvo-home>\tomcat\logs\frevvo.log file:

org.apache.xml.security.encryption.XMLEncryptionException: Illegal key size 
at org.apache.xml.security.encryption.XMLCipher.decryptToByteArray(XMLCipher.java:1822) ~[xmlsec-1.5.7.jar:1.5.7]
…
org.opensaml.xml.encryption.DecryptionException?: Failed to decrypt EncryptedData? 
at org.opensaml.xml.encryption.Decrypter.decryptDataToDOM(Decrypter.java:546) ~[xmltooling-1.4.4.jar:na]
…

Solution:

This error indicates the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files are missing in the Java Development Kit (JDK) software of your on-premise installation. Follow the steps above for the solution.

Retrieving Custom Attributes from LDAP in a SAML Tenant

Similar to the LDAP Security Manager, custom properties in Active Directory for the logged in user can be made available so you can pull them into your form/flow using a business rule. Attributes have to be configured and released in your IDP configuration for them to be available on login.There are several steps that have to happen to accomplish this:

1. Make sure Authentication Only is unchecked in your SAML tenant.
2. Make sure the custom attribute(s) are configured in Active Directory and assigned to the correct users.

3. Configure and release the custom attributes as SAML attributes in your IDP.  

   The procedure to expose custom attributes will differ depending on the IDP you have selected. Refer to your IDP documentation or your on-staff IDP expert to complete this step.

4. Map the attribute with this name in the Custom section of the tenant setup screen.
   1. You can do this when you are creating your SAML tenant or by accessing the Edit Tenant link, after signing on as the tenant admin of your existing SAML tenant.
5. Save the tenant configuration.
6. Write a business rule to populate controls in your form/flow with the information.
   

Example:

Let's take a look at a installation using a SAML tenant, Shibboleth as the IDP and Active Directory for authentication. When the user logs into the SAML tenant, you want to populate these fields in your form with the information from the LDAP server:

These attributes must be configured and released in your IDP. The process to expose the attributes varies for each Identity Provider. In our example, which uses the Shibboleth IDP, configuration and release of the attributes is done in two files, attribute-resolver.xml and attribute-filter.xml. You may need to confer with your on-staff IDP expert to complete this step.

Here is an example of the section of the attribute-resolver.xml file that was added to for the employeeType and employeeNumber custom attributes:

When the attributes are configured in the IDP, add them to the Custom section for attribute mapping by editing/creating your SAML tenant : 

Note the friendly name for the employeeType is listed here while the name of the employeeNumber attribute is used. This was done to match the configuration of the attributes in the IDP.

Next, create your form with fields to collect the attribute information. Include a Dropdown control that will be populated with the groups (roles) that are assigned to the designer user in Active Directory. Add a rule to pull the information into your form:

if(form.load) {
    FirstName.value = _data.getParameter('subject.first.name');
    LastName.value = _data.getParameter('subject.last.name');
    EMail.value = _data.getParameter('subject.email'); 
    EmployeeType.value = _data.getParameter('subject.employeeType');
    EmployeeNumber.value = _data.getParameter('subject.urn:oid:0.9.2342.19200300.100.1.30');
  MemberOf.options =JSON.parse(_data.getParameter('subject.urn:oid:1.3.6.1.4.1.5923.1.1.1.7'));
}

1. In Edit Claim Rules, create a rule to map AD attributes to the outgoing claim type as shown below.  Refer to this website for more information about creating rules to send LDAP attributes as Claims.
   

   1. samAccountName to NameID - If you rather generate an opaque identifier, you would need to create custom rules as described here.
   2. samAccountName to Windows Account Name
   3. givenName to Given Name
   4. Surname to Surname
   5. emailAddresses to Email Address

   6. Group membership is added using the wizard. Select Token-Groups Unqualified Names and map it to the Group claim.