From c11d90593b95f03f4b555af0c10ddf3bb2b262c1 Mon Sep 17 00:00:00 2001
From: Pamela Dragosh <pdragosh@research.att.com>
Date: Thu, 1 Mar 2018 17:11:20 -0500
Subject: Remove CLM issues with commons-collections

We know that we are not configuring an LDAP PIP in our
use of the XACML open source. The LDAP implementation
uses Apache Velocity, which uses a very old version
of commons-collections that has security issues. So
we can exclude commons-collections from the build.

Issue-ID: POLICY-504
Change-Id: I6d90731e601f58c8edaca6fe02df30ee2a090c2f
Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
---
 controlloop/templates/template.demo/pom.xml | 9 +++++++++
 1 file changed, 9 insertions(+)

(limited to 'controlloop/templates/template.demo/pom.xml')

diff --git a/controlloop/templates/template.demo/pom.xml b/controlloop/templates/template.demo/pom.xml
index f2700e7d5..ab6997522 100644
--- a/controlloop/templates/template.demo/pom.xml
+++ b/controlloop/templates/template.demo/pom.xml
@@ -132,6 +132,15 @@
       <artifactId>xacml</artifactId>
       <version>1.0.1</version>
       <scope>test</scope>
+      <exclusions>
+        <!-- The LDAP PIP uses velocity which pulls this insecure jar in. We
+        are not using that PIP and can safely exclude this jar to resolve CLM issue.
+         -->
+        <exclusion>
+          <groupId>commons-collections</groupId>
+          <artifactId>commons-collections</artifactId>
+        </exclusion>
+      </exclusions>
     </dependency>
     <dependency>
       <groupId>com.att.research.xacml</groupId>
-- 
cgit 1.2.3-korg