P4ADEV-507 access organization mode configurable

pagopa · Jun 24, 2024 · b123209 · b123209
1 parent cfcf5a4
commit b123209
Show file tree

Hide file tree

Showing 2 changed files with 10 additions and 1 deletion.
diff --git a/helm/values.yaml b/helm/values.yaml
@@ -65,6 +65,9 @@ microservice-chart:
     REDIS_PORT: "6380"
     REDIS_SSL_ENABLED: "true"
 
+    JWT_TOKEN_EXPIRATION_SECONDS: "14400" # 4 HOURS
+    ENABLE_ACCESS_ORGANIZATION_MODE: "true"
+
   envSecret:
     APPLICATIONINSIGHTS_CONNECTION_STRING: appinsights-connection-string
 

diff --git a/src/main/resources/application.yml b/src/main/resources/application.yml
@@ -35,4 +35,10 @@ management:
         jmx:
             exposure.include: "*"
         web:
-            exposure.include: info, health
+            exposure.include: info, health
+
+app:
+    # If true, it will expect the presence of the access organization inside the ID Token.
+    # Thus it will register te relation between the operator and the relation with the provided roles.
+    # If disabled, the admin should register the associations using the provided API (otherwise they will be disabled)
+    enable-access-organization-mode: "\${ENABLE_ACCESS_ORGANIZATION_MODE:true}"