Deploying Custom Web Application

It is possible to deploy a custom web application inside the DXA container. However, deploying such an application can pose a potential risk, as there’s no guarantee that the application is free from vulnerabilities and can have impact on overall instance security.

Configuration Steps

Within DirX Access Manager, follow these steps to set up a custom web application:

  1. Navigate to Web Applications | Custom section.

  2. Create a new entry, specifying the Context path and Port Assignments for the application.

  3. If you don’t want your application to be excluded from authorization you will have to at least create a resource policy and authentication policy for the application.

    1. Navigate to Policies | Resources section and create a new entry. Choose a PEP identifier, as a Source choose net.atos.dirx.access.apprepo.api.config.client.web.CustomWebApplciation. Choose the Source identifier of the application and specify the URL path.

    2. Next, navigate to Policies | Authentication | Policies and either create a new authentication policy or add the web applications identifier to Resource identifiers of an existing policy.

Deployment of the Web Application

The deployment for a custom web application must be done manually.

  1. Copy the folder with your web application to {installation_folder}/Services/instances/{instance}/webapps/ .

  2. Create an XML configuration for Jetty and add it to {installation_folder}/Services/instances/{instance}/etc/jetty/applications/

  3. Example of such a file is shown below.

    <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure.dtd">
<Configure class="org.eclipse.jetty.webapp.WebAppContext">
  <Set name="contextPath">/{application_context_path}</Set>
  <Set name="war">webapps\{application_folder}</Set>
  <Set name="parentLoaderPriority">false</Set>
</Configure>

  4. Restart the server.