Configuring the hosted transparent decision service

Access to hosted transparent decision services (HTDS) must be secured to use OpenID Connect. You must configure the web.xml file in DecisionService.war and redeploy the WAR file to use HTDS with OpenID Connect.

About this task

The configuration to have secure access to HTDS is already available in the WEB-INF/web.xml file in the DecisionService.war file, but it is disabled by default. You need to uncomment the configuration in the web.xml file to enable it, then deploy the DecisionService.war file.

Procedure

  1. Go to <InstallDir>/executionserver/applicationservers/WLP and decompress the DecisionService.war file.
  2. Open the WEB-INF/web.xml file.
  3. Uncomment the following section in the web.xml file: 
    <!--
<security-constraint xmlns="http://java.sun.com/xml/ns/j2ee">
<web-resource-collection>
    <web-resource-name>Decision Service</web-resource-name>
    <url-pattern>/ws/*</url-pattern>
    <url-pattern>/rest/*</url-pattern>
    <url-pattern>/run</url-pattern>
    <url-pattern>/run.jsp</url-pattern>
    <url-pattern>/swagger</url-pattern>
</web-resource-collection>
<auth-constraint>
    <role-name>resExecutors</role-name>
    </auth-constraint>
</security-constraint>
<login-config xmlns="http://java.sun.com/xml/ns/j2ee">;
    <auth-method>BASIC</auth-method>
    <realm-name>Default</realm-name>
</login-config>
<security-role xmlns="http://java.sun.com/xml/ns/j2ee">;
    <description>The role that is required to use Decision Server Runtime - Executors</description>
    <role-name>resExecutors</role-name>
</security-role>
-->
  4. Save the web.xml file and compress the DecisionService.war file.
  5. Deploy the DecisionService.war file. For more information, see Step 2: Deploying the hosted transparent decision service in the Configuring Rule Execution Server on the Liberty profile section in the product documentation.