frevvo has a pluggable security framework and offers a variety of built-in Security Managers. If you use the frevvo Default Security Manager, a tenant admin can create users and roles directly in your frevvo tenants. See the Manage Users and the Manage Roles for instructions on creating users and roles. Note that with LDAP Security Manager groups are the equivalent of frevvo roles.
frevvo also supports two types of LDAP Security Managers that pull users and groups from your external Active Directory or Open LDAP system and a SAML Security manager that allows enterprises to take advantage of Internet Single Sign On.
- frevvo Security Managers are an Add on feature with additional costs.
- frevvo only supports/certifies Security Managers when frevvo is running in the Apache Tomcat container. Refer to our Supported Platforms for the list of Application Servers supported/certified by frevvo.
- frevvo Default Security Manager - frevvo is responsible for authentication/authorization and managing users/roles. This is the default option. Your tenant will be created with this security manager if no other choice is selected.
- LDAP Active Directory Security Manager - The user is authenticated outside frevvo. frevvo performs the authentication using LDAP directly.
- SAML Security Manager - This security manager allows the exchange of authentication and authorization data between an identity provider of your choice (ex:Shiboleth) and a service provider (frevvo). SSO is supported. Although this security manager can be used on-premise it is primarily meant for cloud tenants who use LDAP but do not want to expose it over the internet.
- Azure SAML Security Manager - This security manager uses SAML in Authentication Only mode and the Active Directory available in the Microsoft Cloud solution, Azure. Integration with the Azure API enables frevvo queries. On-premise AD services can be exposed via Azure providing a clean way to integrate with the frevvo cloud.
- Delegating Security Manager - used for OEM implementations of frevvo.
Which Security Manager do I choose?
Many frevvo customers use the Default Security Manager. All tenants are initially created with this Security Manager. It is the simplest security manager because it does not require integration with an external IDP. Users/roles are managed by the tenant admin.
frevvo offers additional Security Managers, implemented to industry standards, that may be more compatible with your environment. You must have the expertise for setting up your security infrastructure in such a way that whatever choice you make (cloud, ldap, saml, azure) is in fact secure and in compliance with any/all of your auditing requirements.
Selecting a Security Manager for your frevvo tenant is a very important decision. The table helps you make the choice.
| LDAP | SAML | Azure | |
|---|---|---|---|
| Cloud or on-premise | Both - Some organizations do not want to expose LDAP to the internet so they choose on-premise. Read how LDAPs in the cloud is secure. | Both - Primarily used for cloud tenants who do not want to expose their LDAP directly to the internet | Both - provides a simple and secure way to access identity management (azure AD) in the cloud |
Are Users/Roles automatically synchronizied with your frevvo tenant(s) ? | Yes - Manual user/role sync (via frevvo csv upload for example) is not required. The frevvo server automatically gets users & roles from LDAP. | No - if “auth only” mode selected - Users/Roles must be created in your tenant manually. The CSV upload is a good way to do this.
| Yes - Manual user/role sync (via frevvo csv upload for example) is not required. The frevvo server automatically gets users & roles from Azure AD. |
| Single Sign On | Not available frevvo recommends SAML or Azure for SSO | Yes | Yes |
| Authentication Only Mode Choice | No - You must change your IDP (LDAP in this case) to have roles you need in your frevvo workflow if they do not already exist. All user information is maintained in LDAP | Yes | No |
| Authentication Only = Yes | Not Supported | SAML handles authentication only - roles/users managed & maintained via the tenant Users/Roles UI. Changes made via the tenant Users/Roles UI do not get overridden when user logs in/out. You may choose this mode if:
Con - (1) All user information (email address) must be managed by the frevvo tenant admin. This can get out of sync with your IDP. You cannot pull custom attributes from your AD into your forms/workflows in this mode. Pro - You can add roles for frevvo workflow without having to edit your IDP | Users and roles are defined in Azure AD. |
| Authentication Only = No | This is the only mode allowed in this SM and this property does not even exist to change it. Groups needed for these user types in your IDP:
Users are discovered immediately the first time the tenant connects to the IDP and are automatically and always kept in sync without any manual intervention. | Groups needed for these user types in your IDP:
Users discovered when they log in. Changes made via the the tenant Users/Roles UI are overwritten if user logs out then in again. | Users and roles are defined in Azure AD. |
| If your company uses LDAP as your IDP, do you need to install additional software to use this frevvo Security Manager? | No | Yes - (Either install one of the SAML 2.0 Implementations such as ADFS or use a cloud provider such as Okta, and configure it to talk to your LDAP server) | Yes (You must purchase Azure AD in the cloud) |
| Can I embed frevvo forms/workflows into my website with this Security Manager? | Yes | Yes - if the visibility of the form is set to Public. Yes - if the visibility of the form is set to Public in Tenant and the user is already authenticated to SAML No - if the visibility of the form is set to Public in Tenant and the user is NOT already authenticated to SAML. This is because frevvo must direct the user to the IDP login screen and the browser will not allow loading the IDP login page in frevvo's form iframe. | Yes - if the visibility of the form is set to Public. Yes - if the visibility of the form is set to Public in Tenant and the user is already authenticated to Azure SAML. No - if the visibility of the form is set to Public in Tenant and the user is NOT already authenticated to Azure SAML. This is because frevvo must direct the user to the IDP login screen and the browser will not allow loading the IDP login page in frevvo's form iframe. |
| What does frevvo support? | Microsoft AD, Open LDAP | Shibboleth, ADFS, Okta, Centrify, Google and any other software that implements the SAML 2.0 protocol | There is no other implementation of Azure AD then Azure AD |
| What does frevvo certify? | Microsoft AD | none | Azure AD |
| Do you need your own Configuration Specialist for your IDP | Yes | Yes | Yes |
Changing the Security Manager for your Tenant
frevvo trial tenants are configured with the default security manager. Once you have purchased a license for your frevvo tenant the original security manager can be changed. This allows you to keep the submissions and the name of your existing tenant.
Cloud customers planning to switch the Security Manager of your tenant from the default to the LDAP, SAML or Azure SAML Security Managers or a tenant using the SAML security manager on a trial basis should contact sales@frevvo.com to initiate the process.
Tenants using the Default Security Manager can be migrated to:
- Default Security Manager → LDAP
- Default Security Manager → SAML
- Default Security Manager → Azure SAML
Tenants using the LDAP Security Manager can migrate to:
- LDAP → SAML
LDAP → Azure SAML
Projects, forms, workflows, submissions, and portals are maintained in users' accounts. If your usernames will change as a result of changing security managers, the original designer user(s)/owner(s) will not be able to access them. Before you change your Security Manager, you must take steps to ensure continued access to your existing resources. We recommend that you download the Projects/Forms/Workflows that you want to preserve to your desktop as a backup BEFORE changing the Security Manager. frevvo Best Practice recommends that you create a user account in your Active Directory/IDP that will house all of your deployed Production forms/workflows. This user can be named anything (e.g., frevvoProduction) but it must be a member of the frevvo.Designer group. First, answer these questions. Preserve Projects/Forms/Workflows developed in your trial/starter tenant with three easy migration steps. These steps will not preserve submissions. Preserve access to your production Projects/Forms/Workflows and submissions by creating a generic user in your IDP who will have access to the existing resources. Preserve access to your original designer user's resources by accessing their designer home page via a saved URL (only available to logged-in Admin users.) After you change Security Managers, the tenant admin will be able to access this URL in order to view or edit existing resources. The admin user must be logged in to access the URL. If your form/workflow Access Control settings, Step Assignments, Business Rules, or controls (e.g. a dropdown control) refer to hard-coded user/role assignments, you will need to update those to use the new LDAP(s)/SAML/Azure user/role IDs immediately after changing the Security Manager. "Old" user/role id references can lead to invalid task assignments and can limit user access to your forms/workflows. Pending tasks assigned to “old” users/roles will need to be modified and reassigned by the workflow or tenant admin.Preserve Access to Forms and Workflows
Production User
Evaluate User/Role Set Up
Option 1 Migrate Forms and Workflows, Leave Behind Submissions and Portals
Option 2 Create a Production User in your IDP and Give them Access to Forms and Workflows
Option 3 Access Original Designer User via Admin User
Other Considerations