Submit a ticketCall us

Systems Monitoring for Dummies
Our new eBook will teach you the fundamentals and help you create monitors and alerts that are effective, meaningful, and actionable. Monitoring is more than a checkbox on your to-do list. This free eBook will give you practical advice to help you succeed in all aspects of monitoring – discovery, alerting, remediation, and troubleshooting. Don’t miss out on this indispensable resource for newbies, experienced IT pros, and everyone in between. Register Now.

Home > Success Center > Web Help Desk (WHD) > Configure the CAS module for LDAP and Active Directory

Configure the CAS module for LDAP and Active Directory

 

Overview

The Central Authentication Service (CAS) is a single sign-on protocol that enables a user to access multiple applications using one set of credentials. This protocol works in conjunction with the CAS server, which handles all the user connections to your Microsoft Exchange and LDAP servers.

You can deploy CAS server into Apache Tomcat on Web Help Desk or your own Web Help Desk server. Before you deploy single sign-on (SSO) with CAS 2.0 in your Web Help Desk deployment, follow the procedures in this article to configure the CAS module for LDAP and Active Directory communications.

Environment

  • Web Help Desk 12.4.x and later

Steps

To deploy CAS server on your Apache Tomcat server:

  1. Download the Jasiq CAS server web application file.
  2. Update the file using the attached text files in this article and set it up based on your system configuration.
  3. Download and apply the dependencies.
  4. Deploy CAS server on your Apache Tomcat server. 
  5. Complete your CAS server deployment. 

Download the CAS Server file

  1. Download the cas-server-webapp-3.5.2.zip file from the Apereo website.
  2. Open the ZIP file and navigate to cas-server-3.5.2\modules
  3. Extract cas-server-webapp-3.5.2.war from the modules directory.

Update the file

  1. Rename the cas-server-webapp-3.5.2.war file to cas.zip
  2. Open the ZIP file as an archive. 
  3. Open the WEB-INF directory.
  4. Open the deployerConfigContext file in Notepad.
  5. Download and open the deployerconfigcontext.txt file attached to this article. 
  6. Copy the file contents to the deployerConfigContext file, overwriting the existing content.
  7. In the updated deployerConfigContext file, update the file variables for your deployment. 
    1. Locate the following argument:

      <property name="url" value="ldap://127.0.0.1:389" /> 
      <!-- use ‘ldaps://’ for ssl connection -->
    2. Replace the value variable with the IP address of your LDAP server. 
    3. Locate the following argument:
      <property name="userDn" value="ldap_admin@yourdomain.com" />
    4. Replace the value variable with the email address of your LDAP administrator.
    5. Locate the following argument:
      <property name="password" value="ldap_admin_password" />
    6. Replace the value variable with your LDAP admin password.
    7. Locate the following argument:
      p:filter="sAMAccountName=%u" p:searchBase="DC=yourdomain,DC=com"
    8. Ensure that the LDAP p:filter search filter matches your LDAP configuration settings. 
    9. Replace the p:searchBase variables with your domain information.  
    10. Close the file. 
  8. Open the cas.properties file in Notepad.
  9. Download and open the casproperties.txt file attached to this article. 
  10. Copy and paste the file contents to the cas.properties file.
  11. In the updated cas.properties file, update the file variables for your deployment. 
    1. Locate the following argument:
      server.name=http://localhost:8080
    2. Replace the server.hame variable with a WHD server address. For example:
      http://whd.yourdomain.com
    3. Locate the following argument:
      host.name=cas01.yourdomain.com
    4. Replace the host.name variable with the provided prefix and your domain name.
    5. Close the file. 

Download and apply the dependencies

  1. Download the following dependencies in JAR format:
  2. Open the cas.zip file and navigate to the WEB-INF/lib/ directory. 
  3. Copy all dependencies to the directory. 
  4. Rename the cas.zip file to cas.war.

Deploy CAS server on Apache Tomcat

  1. Stop the Web Help Desk Service.
    1. Open File Explorer and navigate to the <WebHelpDesk> directory.
    2. Double-click whd_stop.bat.

      The Web Help Desk service is stopped.

  2. Copy the cas.war file to the /bin/webapps directory on your Apache Tomcat deployment.
  3. Start the Web Help Desk Service.
    1. Open the <WebHelpDesk> directory.
    2. Double-click whd_start.bat.

      The Web Help Desk Service is started. 

      CAS 2.0 is now accessible from the following URL:

      https://webhelpdesk:port/cas
  4. Verify that the HTTPS port is enabled on Apache Tomcat.

    If the port is not enabled, see "Enable SSL on Web Help Desk" in Deploy SSO with CAS 2.0.

    If the HTTPS port is enabled, see "Deploy CAS 2.0 on the Web Help Desk server" in Deploy SSO with CAS 2.0.

Complete your CAS server deployment

Configure a Group Policy Object (GPO) to push the appropriate Windows login credentials to your Internet Explorer settings. This process allows authenticated users to access the Web Help Desk server without having to log in. GPOs define the settings for your Windows server configuration, and Group Policies apply these settings.

See "Configure a GPO to push Internet Explorer settings" in Deploy SSO with CAS 2.0 for more information. 

 

 

Last modified

Tags

Classifications

Public