From caead0115fa286d6796ad749464e8df09f383338 Mon Sep 17 00:00:00 2001
From: Pamela Dragosh <pdragosh@research.att.com>
Date: Thu, 1 Mar 2018 18:00:06 -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-507
Change-Id: I735eae4fe507ad016d9b0b49e67536415edb9820
Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
---
 ONAP-PDP/pom.xml | 9 +++++++++
 1 file changed, 9 insertions(+)

(limited to 'ONAP-PDP')

diff --git a/ONAP-PDP/pom.xml b/ONAP-PDP/pom.xml
index d302c955d..dc3953b76 100644
--- a/ONAP-PDP/pom.xml
+++ b/ONAP-PDP/pom.xml
@@ -73,6 +73,15 @@
 			<groupId>com.att.research.xacml</groupId>
 			<artifactId>xacml-pdp</artifactId>
 			<version>1.0.1</version>
+            <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>junit</groupId>
-- 
cgit 1.2.3-korg