From 4664e0a9c14f1753d348b993dc01133605fc5f83 Mon Sep 17 00:00:00 2001 From: PatrikBuhr Date: Wed, 27 Apr 2022 15:16:25 +0200 Subject: [PATCH] Uplift from ONAP. Usage of authorization token. Signed-off-by: PatrikBuhr Issue-ID: NONRTRIC-743 Change-Id: I7a1a5d50c992e5ad3f7f8a1a7b8ab48276145c5b --- config/application.yaml | 3 +++ onap/oran | 2 +- pom.xml | 2 +- 3 files changed, 5 insertions(+), 2 deletions(-) diff --git a/config/application.yaml b/config/application.yaml index 5684c46..54f47e0 100644 --- a/config/application.yaml +++ b/config/application.yaml @@ -77,4 +77,7 @@ app: # the config-file-schema-path referres to a location in the jar file. If this property is empty or missing, # no schema validation will be executed. config-file-schema-path: /application_configuration_schema.json + # A file containing an authorization token, which shall be inserted in each HTTP header (authorization). + # If the file name is empty, no authorization token is sent. + auth-token-file: diff --git a/onap/oran b/onap/oran index 4b62052..e9ddfb1 160000 --- a/onap/oran +++ b/onap/oran @@ -1 +1 @@ -Subproject commit 4b6205245fd4839e4449e26aa4e3000ddb30ecc1 +Subproject commit e9ddfb1e0e0b256986d24aa02129e2e3850bb480 diff --git a/pom.xml b/pom.xml index 12b8ecd..1737952 100644 --- a/pom.xml +++ b/pom.xml @@ -48,7 +48,7 @@ 11 3.0.0 - 2.8.2 + 2.8.8 2.1.13 20211205 3.8.0 -- 2.16.6