---
title: "Configure Client Application for CaSS"
slug: "configure-client-application-for-cass"
tags: ["IT Pro"]
updated: 2026-10-30T08:16:57Z
published: 2026-10-30T08:16:57Z
canonical: "help.lanteria.com/configure-client-application-for-cass"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.lanteria.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Configure Client Application for CaSS

Follow these steps to configure the client application:

1. Copy the Lanteria.ApplicantSelfService.App folder to "C:\inetpub\wwwroot".
2. Create another web application in IIS Manager:  
Specify the site name (for example, ApplicantSelfServiceClientApp), application pool, and physical path (C:\inetpub\wwwroot\Lanteria.ApplicantSelfService.App). Set up the HTTPS binding.  
![](https://cdn.document360.io/c315c68d-2799-4fcc-9a39-084315b58f14/Images/Documentation/img009(8).png)
3. Make the following changes to the **appsettings.****jso****n** file:
  - In IIS Manager, right-click ApplicantSelfServiceClientApp > Explore.
  - Open appsettings.json in a text editor.
  - In the ApiConfiguration section, set the Endpoint property to the URL of the API service that you have configured during the [previous step](/v1/docs/configure-api-service-for-cass). For example: https://your_domain:port/api, where **your_domain** is your localhost or domain name, and **port** is the port number.
  - In the **LanteriaHRConfiguration** section, set the Endpoint property to the URL specified in the **HttpHandlerURL** property.
  - In the SmtpConfiguration section, specify the configuration data for SMTP.

## Application Pool Configuration

We recommend the following configuration of the application pools:

1. Do not assign the application pool to a specific user (especially one with admin permissions); use ApplicationPoolIdentity as the identity.
2. Do not use a single application pool for all applications; run Lanteria HR and Candidate Self-Service on separate application pools.
3. The application and API parts of Candidate Self-Service may share the same application pool, but they can't share a pool with Lanteria HR (this statement is applicable for Candidate Self-Service running on .NET Core 10 and higher; if you are using older versions, you may use a single application pool for all applications).

## Extended Web Application to use NTLM Authentication

Lanteria HR supports several authentication types: NTLM, forms-based, and external providers. Candidate Self-Service supports only NTLM authentication.

If your Lanteria HR web application does not have NTLM authentication enabled, you must [extend the](https://docs.microsoft.com/en-us/sharepoint/administration/extend-a-claims-based-web-application) Lanteria HR web application to create an additional endpoint that will use NTLM authentication. Make sure that Candidate Self-Service is also configured for this extended web application.