Last Updated on

Ephesoft configuration with ADFS over SAML 2.0 with Authentication Type 1 and Authorization using Active Directory

This wiki provides you details related to what all configuration needs to be taken care of when configuring Ephesoft with ADFS over SAML 2.0 with Authentication Type 1. Authentication Type 1 means we are authenticating using SSO but authorizing using Tomcat, LDAP or Active Directory. In this article we will focus on Authorization with Active Directory.

 

How Does Authentication with SSO and Authorization with Active Directory works ?

  • We only provide authentication details to the Identity Provider.
  • Identity provider verifies the validity of the user and sends back acknowledgement as a part of SAML Response.
  • If validation is successful the selected Authorization method is taken into consideration. If user.connection is set to value 1 then authorization happens using Active Directory.
  • Username received as response is matched with the groups / roles fetched from Active Directory.
  • This role matches with user.super_admin property in application.properties and if match is good then the user is provided with super admin access else user gets access based on the Roles defined Access Manager.

 

Pre-requisite:

  1. Active Directory Federation Services Installed
  2. Active Directory Installed.
  3. Ephesoft Transact 4.5.0.0 or onwards Installed
  4. Understanding and already configured the files as mentioned in Checklist: Ephesoft with ADFS over SAML 2.0 with Authentication Type 1 and Authorization using Tomcat article.

 

Configuration Files Required

  1. Already listed files in wiki article Checklist: Ephesoft with ADFS over SAML 2.0 with Authentication Type 1 and Authorization using Tomcat
  2. Configuration changes are required in application.properties, server.xml and user-connectivity.properties file

 

Checklist components:


Existing Configuration:


Additional changes:

Server.xml

  • Add the realm configuration for Active Directory as shown in the screenshot below

Note:

  1. Please note that you need to change connectionURL, connectionName, connectionPassword, userBase, roleBase properties as per your Active Directory structure. 
  2. Download the sample server.xml from here

user-connectivity.properties

  • Make required changes in user-connectivity.properties file as shown in the screenshot below

 

Note:

  1. Please note that you need to change the properties as per your Active Directory structure. 
  2. Download the sample user-connectivity.properties from here.

application.properties

  • This file is used to define Super Admin Group Names.
  • Two properties that require change is  user.super_admin where we define super admin groups and update_super_admin_group where we will need to change the flag to true.

Was this article helpful to you?

Abhishek Jain