From 537c230a5113513fceccb62dfe471e60d39d1ab1 Mon Sep 17 00:00:00 2001
From: Pamela Dragosh <pdragosh@research.att.com>
Date: Fri, 2 Nov 2018 11:10:27 -0400
Subject: [PATCH] Upgrade xacml 1.0.2

This version of xacml only has license changes to the java
source files. This will clear ONAP license issues.

Issue-ID: POLICY-1228
Change-Id: I7496fc54e44a51f89e438adaa1ab70a1c23aa06d
Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
(cherry picked from commit 510c439f70556718f9fceeb6bad1a771ccbb410c)
---
 BRMSGateway/dependency.json | 2 +-
 ONAP-PDP/pom.xml            | 2 +-
 ONAP-XACML/pom.xml          | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/BRMSGateway/dependency.json b/BRMSGateway/dependency.json
index b7513243b..b8e3e7cd3 100644
--- a/BRMSGateway/dependency.json
+++ b/BRMSGateway/dependency.json
@@ -120,7 +120,7 @@
         }, {
             "groupId": "com.att.research.xacml",
             "artifactId": "xacml-pdp",
-            "version": "1.0.1"
+            "version": "1.0.2"
         }]
     }
 }
diff --git a/ONAP-PDP/pom.xml b/ONAP-PDP/pom.xml
index a4fa7c8ca..d4f2b561a 100644
--- a/ONAP-PDP/pom.xml
+++ b/ONAP-PDP/pom.xml
@@ -65,7 +65,7 @@
         <dependency>
             <groupId>com.att.research.xacml</groupId>
             <artifactId>xacml-pdp</artifactId>
-            <version>1.0.1</version>
+            <version>1.0.2</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. -->
diff --git a/ONAP-XACML/pom.xml b/ONAP-XACML/pom.xml
index 980908916..06f532f3b 100644
--- a/ONAP-XACML/pom.xml
+++ b/ONAP-XACML/pom.xml
@@ -50,7 +50,7 @@
         <dependency>
             <groupId>com.att.research.xacml</groupId>
             <artifactId>xacml</artifactId>
-            <version>1.0.1</version>
+            <version>1.0.2</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.
-- 
2.16.6