diff --git a/agama/pom.xml b/agama/pom.xml index c10d0bf968e..e7310776ee3 100644 --- a/agama/pom.xml +++ b/agama/pom.xml @@ -5,7 +5,7 @@ io.jans agama pom - 1.1.4-SNAPSHOT + 1.1.4 agama parent diff --git a/agama/transpiler/pom.xml b/agama/transpiler/pom.xml index be5f53f0184..4018bc2037d 100644 --- a/agama/transpiler/pom.xml +++ b/agama/transpiler/pom.xml @@ -9,7 +9,7 @@ io.jans agama - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/charts/janssen-all-in-one/Chart.yaml b/charts/janssen-all-in-one/Chart.yaml index c547264942a..2c119570344 100644 --- a/charts/janssen-all-in-one/Chart.yaml +++ b/charts/janssen-all-in-one/Chart.yaml @@ -3,14 +3,14 @@ annotations: artifacthub.io/containsSecurityUpdates: 'true' artifacthub.io/images: | - name: all-in-one - image: ghcr.io/janssenproject/jans/all-in-one:1.1.4_dev + image: ghcr.io/janssenproject/jans/all-in-one:1.1.4-1 artifacthub.io/license: Apache-2.0 artifacthub.io/prerelease: 'false' catalog.cattle.io/certified: partner catalog.cattle.io/release-name: janssen-all-in-one catalog.cattle.io/display-name: Janssen Cloud Identity and Access Management All-in-One apiVersion: v2 -appVersion: "1.1.4-dev" +appVersion: "1.1.4" icon: >- https://raw.githubusercontent.com/JanssenProject/jans/main/docs/assets/logo/janssen_project_favicon_transparent_50px_50px.png home: https://jans.io @@ -22,4 +22,4 @@ maintainers: email: support@jans.io description: Janssen Access and Identity Management All-in-One Chart. This chart deploys the selected janssen microservice all in one deployment. name: janssen-all-in-one -version: 1.1.4-dev +version: 1.1.4 diff --git a/charts/janssen-all-in-one/README.md b/charts/janssen-all-in-one/README.md index e63dcbcc36e..6449c129ac6 100644 --- a/charts/janssen-all-in-one/README.md +++ b/charts/janssen-all-in-one/README.md @@ -1,6 +1,6 @@ # janssen-all-in-one -![Version: 1.1.4-dev](https://img.shields.io/badge/Version-1.1.4--dev-informational?style=flat-square) ![AppVersion: 1.1.4-dev](https://img.shields.io/badge/AppVersion-1.1.4--dev-informational?style=flat-square) +![Version: 1.1.4](https://img.shields.io/badge/Version-1.1.4-informational?style=flat-square) ![AppVersion: 1.1.4](https://img.shields.io/badge/AppVersion-1.1.4-informational?style=flat-square) Janssen Access and Identity Management All-in-One Chart. This chart deploys the selected janssen microservice all in one deployment. @@ -30,7 +30,7 @@ Kubernetes: `>=v1.22.0-0` | adminPassword | string | `"Test1234#"` | Admin password to log in to the UI. | | alb.ingress | bool | `false` | switches the service to Nodeport for ALB ingress | | auth-server | object | `{"appLoggers":{"auditStatsLogLevel":"INFO","auditStatsLogTarget":"FILE","authLogLevel":"INFO","authLogTarget":"STDOUT","enableStdoutLogPrefix":"true","httpLogLevel":"INFO","httpLogTarget":"FILE","ldapStatsLogLevel":"INFO","ldapStatsLogTarget":"FILE","persistenceDurationLogLevel":"INFO","persistenceDurationLogTarget":"FILE","persistenceLogLevel":"INFO","persistenceLogTarget":"FILE","scriptLogLevel":"INFO","scriptLogTarget":"FILE"},"authEncKeys":"RSA1_5 RSA-OAEP","authSigKeys":"RS256 RS384 RS512 ES256 ES384 ES512 PS256 PS384 PS512","enabled":true,"ingress":{"authServerAdditionalAnnotations":{},"authServerEnabled":true,"authServerLabels":{},"deviceCodeAdditionalAnnotations":{},"deviceCodeEnabled":true,"deviceCodeLabels":{},"firebaseMessagingAdditionalAnnotations":{},"firebaseMessagingEnabled":true,"firebaseMessagingLabels":{},"lockAdditionalAnnotations":{},"lockConfigAdditionalAnnotations":{},"lockConfigEnabled":false,"lockConfigLabels":{},"lockEnabled":false,"lockLabels":{},"openidAdditionalAnnotations":{},"openidConfigEnabled":true,"openidConfigLabels":{},"u2fAdditionalAnnotations":{},"u2fConfigEnabled":true,"u2fConfigLabels":{},"uma2AdditionalAnnotations":{},"uma2ConfigEnabled":true,"uma2ConfigLabels":{},"webdiscoveryAdditionalAnnotations":{},"webdiscoveryEnabled":true,"webdiscoveryLabels":{},"webfingerAdditionalAnnotations":{},"webfingerEnabled":true,"webfingerLabels":{}},"lockEnabled":false}` | Parameters used globally across all services helm charts. | -| auth-server-key-rotation | object | `{"additionalAnnotations":{},"additionalLabels":{},"customScripts":[],"dnsConfig":{},"dnsPolicy":"","enabled":true,"image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"ghcr.io/janssenproject/jans/certmanager","tag":"1.1.4_dev"},"initKeysLife":48,"keysLife":48,"keysPushDelay":0,"keysPushStrategy":"NEWER","keysStrategy":"NEWER","lifecycle":{},"resources":{"limits":{"cpu":"300m","memory":"300Mi"},"requests":{"cpu":"300m","memory":"300Mi"}},"usrEnvs":{"normal":{},"secret":{}},"volumeMounts":[],"volumes":[]}` | Responsible for regenerating auth-keys per x hours | +| auth-server-key-rotation | object | `{"additionalAnnotations":{},"additionalLabels":{},"customScripts":[],"dnsConfig":{},"dnsPolicy":"","enabled":true,"image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"ghcr.io/janssenproject/jans/certmanager","tag":"1.1.4-1"},"initKeysLife":48,"keysLife":48,"keysPushDelay":0,"keysPushStrategy":"NEWER","keysStrategy":"NEWER","lifecycle":{},"resources":{"limits":{"cpu":"300m","memory":"300Mi"},"requests":{"cpu":"300m","memory":"300Mi"}},"usrEnvs":{"normal":{},"secret":{}},"volumeMounts":[],"volumes":[]}` | Responsible for regenerating auth-keys per x hours | | auth-server-key-rotation.additionalAnnotations | object | `{}` | Additional annotations that will be added across the gateway in the format of {cert-manager.io/issuer: "letsencrypt-prod"} | | auth-server-key-rotation.additionalLabels | object | `{}` | Additional labels that will be added across the gateway in the format of {mylabel: "myapp"} | | auth-server-key-rotation.customScripts | list | `[]` | Add custom scripts that have been mounted to run before the entrypoint. - /tmp/custom.sh - /tmp/custom2.sh | @@ -40,7 +40,7 @@ Kubernetes: `>=v1.22.0-0` | auth-server-key-rotation.image.pullPolicy | string | `"IfNotPresent"` | Image pullPolicy to use for deploying. | | auth-server-key-rotation.image.pullSecrets | list | `[]` | Image Pull Secrets | | auth-server-key-rotation.image.repository | string | `"ghcr.io/janssenproject/jans/certmanager"` | Image to use for deploying. | -| auth-server-key-rotation.image.tag | string | `"1.1.4_dev"` | Image tag to use for deploying. | +| auth-server-key-rotation.image.tag | string | `"1.1.4-1"` | Image tag to use for deploying. | | auth-server-key-rotation.initKeysLife | int | `48` | The initial auth server key rotation keys life in hours | | auth-server-key-rotation.keysLife | int | `48` | Auth server key rotation keys life in hours | | auth-server-key-rotation.keysPushDelay | int | `0` | Delay (in seconds) before pushing private keys to Auth server | @@ -265,7 +265,7 @@ Kubernetes: `>=v1.22.0-0` | image.pullPolicy | string | `"IfNotPresent"` | Image pullPolicy to use for deploying. | | image.pullSecrets | list | `[]` | Image Pull Secrets | | image.repository | string | `"ghcr.io/janssenproject/jans/all-in-one"` | Image to use for deploying. | -| image.tag | string | `"1.1.4_dev"` | Image tag to use for deploying. | +| image.tag | string | `"1.1.4-1"` | Image tag to use for deploying. | | isFqdnRegistered | bool | `false` | Boolean flag to enable mapping lbIp to fqdn inside pods on clouds that provide static ip for load balancers. On cloud that provide only addresses to the LB this flag will enable a script to actively scan config.configmap.lbAddr and update the hosts file inside the pods automatically. | | istio.additionalAnnotations | object | `{}` | Additional annotations that will be added across the gateway in the format of {cert-manager.io/issuer: "letsencrypt-prod"} | | istio.additionalLabels | object | `{}` | Additional labels that will be added across the gateway in the format of {mylabel: "myapp"} | @@ -274,7 +274,7 @@ Kubernetes: `>=v1.22.0-0` | istio.ingress | bool | `false` | Boolean flag that enables using istio gateway for Janssen. This assumes istio ingress is installed and hence the LB is available. | | istio.namespace | string | `"istio-system"` | The namespace istio is deployed in. The is normally istio-system. | | istio.tlsSecretName | string | `"istio-tls-certificate"` | | -| kc-scheduler | object | `{"additionalAnnotations":{},"additionalLabels":{},"customScripts":[],"dnsConfig":{},"dnsPolicy":"","enabled":false,"image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"ghcr.io/janssenproject/jans/kc-scheduler","tag":"1.1.4_dev"},"interval":10,"lifecycle":{},"resources":{"limits":{"cpu":"300m","memory":"300Mi"},"requests":{"cpu":"300m","memory":"300Mi"}},"usrEnvs":{"normal":{},"secret":{}},"volumeMounts":[],"volumes":[]}` | Responsible for synchronizing Keycloak SAML clients | +| kc-scheduler | object | `{"additionalAnnotations":{},"additionalLabels":{},"customScripts":[],"dnsConfig":{},"dnsPolicy":"","enabled":false,"image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"ghcr.io/janssenproject/jans/kc-scheduler","tag":"1.1.4-1"},"interval":10,"lifecycle":{},"resources":{"limits":{"cpu":"300m","memory":"300Mi"},"requests":{"cpu":"300m","memory":"300Mi"}},"usrEnvs":{"normal":{},"secret":{}},"volumeMounts":[],"volumes":[]}` | Responsible for synchronizing Keycloak SAML clients | | kc-scheduler.additionalAnnotations | object | `{}` | Additional annotations that will be added across the gateway in the format of {cert-manager.io/issuer: "letsencrypt-prod"} | | kc-scheduler.additionalLabels | object | `{}` | Additional labels that will be added across the gateway in the format of {mylabel: "myapp"} | | kc-scheduler.customScripts | list | `[]` | Add custom scripts that have been mounted to run before the entrypoint. - /tmp/custom.sh - /tmp/custom2.sh | @@ -284,7 +284,7 @@ Kubernetes: `>=v1.22.0-0` | kc-scheduler.image.pullPolicy | string | `"IfNotPresent"` | Image pullPolicy to use for deploying. | | kc-scheduler.image.pullSecrets | list | `[]` | Image Pull Secrets | | kc-scheduler.image.repository | string | `"ghcr.io/janssenproject/jans/kc-scheduler"` | Image to use for deploying. | -| kc-scheduler.image.tag | string | `"1.1.4_dev"` | Image tag to use for deploying. | +| kc-scheduler.image.tag | string | `"1.1.4-1"` | Image tag to use for deploying. | | kc-scheduler.interval | int | `10` | Interval of running the scheduler (in minutes) | | kc-scheduler.resources | object | `{"limits":{"cpu":"300m","memory":"300Mi"},"requests":{"cpu":"300m","memory":"300Mi"}}` | Resource specs. | | kc-scheduler.resources.limits.cpu | string | `"300m"` | CPU limit. | @@ -377,4 +377,4 @@ Kubernetes: `>=v1.22.0-0` | volumes | list | `[]` | Configure any additional volumes that need to be attached to the pod | ---------------------------------------------- -Autogenerated from chart metadata using [helm-docs v1.12.0](https://github.com/norwoodj/helm-docs/releases/v1.12.0) +Autogenerated from chart metadata using [helm-docs v1.11.0](https://github.com/norwoodj/helm-docs/releases/v1.11.0) diff --git a/charts/janssen-all-in-one/values.yaml b/charts/janssen-all-in-one/values.yaml index ea5c2e1e809..63b8a24ed4d 100644 --- a/charts/janssen-all-in-one/values.yaml +++ b/charts/janssen-all-in-one/values.yaml @@ -319,7 +319,7 @@ auth-server-key-rotation: # -- Image to use for deploying. repository: ghcr.io/janssenproject/jans/certmanager # -- Image tag to use for deploying. - tag: 1.1.4_dev + tag: 1.1.4-1 # -- Image Pull Secrets pullSecrets: [ ] # -- Auth server key rotation keys life in hours @@ -700,7 +700,7 @@ image: # -- Image to use for deploying. repository: ghcr.io/janssenproject/jans/all-in-one # -- Image tag to use for deploying. - tag: 1.1.4_dev + tag: 1.1.4-1 # -- Image Pull Secrets pullSecrets: [ ] # -- Service replica number. @@ -778,7 +778,7 @@ kc-scheduler: # -- Image to use for deploying. repository: ghcr.io/janssenproject/jans/kc-scheduler # -- Image tag to use for deploying. - tag: 1.1.4_dev + tag: 1.1.4-1 # -- Image Pull Secrets pullSecrets: [ ] # -- Resource specs. diff --git a/charts/janssen/Chart.yaml b/charts/janssen/Chart.yaml index 1246aa080b0..65a589f42bb 100644 --- a/charts/janssen/Chart.yaml +++ b/charts/janssen/Chart.yaml @@ -3,36 +3,36 @@ annotations: artifacthub.io/containsSecurityUpdates: 'true' artifacthub.io/images: | - name: auth-server - image: ghcr.io/janssenproject/jans/auth-server:1.1.4_dev + image: ghcr.io/janssenproject/jans/auth-server:1.1.4-1 - name: auth-server-key-rotation - image: ghcr.io/janssenproject/jans/certmanager:1.1.4_dev + image: ghcr.io/janssenproject/jans/certmanager:1.1.4-1 - name: configuration-manager - image: ghcr.io/janssenproject/jans/configurator:1.1.4_dev + image: ghcr.io/janssenproject/jans/configurator:1.1.4-1 - name: config-api - image: ghcr.io/janssenproject/jans/config-api:1.1.4_dev + image: ghcr.io/janssenproject/jans/config-api:1.1.4-1 - name: fido2 - image: ghcr.io/janssenproject/jans/fido2:1.1.4_dev + image: ghcr.io/janssenproject/jans/fido2:1.1.4-1 - name: opendj image: gluufederation/opendj:5.0.0_dev - name: persistence - image: ghcr.io/janssenproject/jans/persistence-loader:1.1.4_dev + image: ghcr.io/janssenproject/jans/persistence-loader:1.1.4-1 - name: casa - image: ghcr.io/janssenproject/jans/casa:1.1.4_dev + image: ghcr.io/janssenproject/jans/casa:1.1.4-1 - name: scim - image: ghcr.io/janssenproject/jans/scim:1.1.4_dev + image: ghcr.io/janssenproject/jans/scim:1.1.4-1 - name: link - image: ghcr.io/janssenproject/jans/link:1.1.4_dev + image: ghcr.io/janssenproject/jans/link:1.1.4-1 - name: saml - image: ghcr.io/janssenproject/jans/saml:1.1.4_dev + image: ghcr.io/janssenproject/jans/saml:1.1.4-1 - name: kc-scheduler - image: ghcr.io/janssenproject/jans/kc-scheduler:1.1.4_dev + image: ghcr.io/janssenproject/jans/kc-scheduler:1.1.4-1 artifacthub.io/license: Apache-2.0 artifacthub.io/prerelease: 'false' catalog.cattle.io/certified: partner catalog.cattle.io/release-name: janssen catalog.cattle.io/display-name: Janssen Cloud Identity and Access Management Microservices apiVersion: v2 -appVersion: "1.1.4-dev" +appVersion: "1.1.4" icon: >- https://raw.githubusercontent.com/JanssenProject/jans/main/docs/assets/logo/janssen_project_favicon_transparent_50px_50px.png home: https://jans.io @@ -44,60 +44,60 @@ maintainers: email: support@jans.io description: Janssen Access and Identity Management Microservices Chart. This chart deploys each janssen microservice as a separate deployment. name: janssen -version: 1.1.4-dev +version: 1.1.4 dependencies: - name: casa - version: 1.1.4-dev + version: 1.1.4 condition: global.casa.enabled - name: config condition: global.config.enabled - version: 1.1.4-dev + version: 1.1.4 - name: config-api condition: global.config-api.enabled - version: 1.1.4-dev + version: 1.1.4 - name: opendj condition: global.opendj.enabled - version: 1.1.4-dev + version: 1.1.4 - name: auth-server condition: global.auth-server.enabled - version: 1.1.4-dev + version: 1.1.4 - name: fido2 condition: global.fido2.enabled - version: 1.1.4-dev + version: 1.1.4 - name: scim condition: global.scim.enabled - version: 1.1.4-dev + version: 1.1.4 - name: nginx-ingress condition: global.nginx-ingress.enabled - version: 1.1.4-dev + version: 1.1.4 - name: auth-server-key-rotation condition: global.auth-server-key-rotation.enabled - version: 1.1.4-dev + version: 1.1.4 - name: persistence condition: global.persistence.enabled - version: 1.1.4-dev + version: 1.1.4 - name: link condition: global.link.enabled - version: 1.1.4-dev + version: 1.1.4 - name: saml condition: global.saml.enabled - version: 1.1.4-dev + version: 1.1.4 - name: cn-istio-ingress condition: global.istio.ingress - version: 1.1.4-dev + version: 1.1.4 - name: kc-scheduler condition: global.kc-scheduler.enabled - version: 1.1.4-dev + version: 1.1.4 diff --git a/charts/janssen/README.md b/charts/janssen/README.md index 3c8c2dff321..9b26e161f6f 100644 --- a/charts/janssen/README.md +++ b/charts/janssen/README.md @@ -1,6 +1,6 @@ # janssen -![Version: 1.1.4-dev](https://img.shields.io/badge/Version-1.1.4--dev-informational?style=flat-square) ![AppVersion: 1.1.4-dev](https://img.shields.io/badge/AppVersion-1.1.4--dev-informational?style=flat-square) +![Version: 1.1.4](https://img.shields.io/badge/Version-1.1.4-informational?style=flat-square) ![AppVersion: 1.1.4](https://img.shields.io/badge/AppVersion-1.1.4-informational?style=flat-square) Janssen Access and Identity Management Microservices Chart. This chart deploys each janssen microservice as a separate deployment. @@ -23,27 +23,27 @@ Kubernetes: `>=v1.22.0-0` | Repository | Name | Version | |------------|------|---------| -| | auth-server | 1.1.4-dev | -| | auth-server-key-rotation | 1.1.4-dev | -| | casa | 1.1.4-dev | -| | cn-istio-ingress | 1.1.4-dev | -| | config | 1.1.4-dev | -| | config-api | 1.1.4-dev | -| | fido2 | 1.1.4-dev | -| | kc-scheduler | 1.1.4-dev | -| | link | 1.1.4-dev | -| | nginx-ingress | 1.1.4-dev | -| | opendj | 1.1.4-dev | -| | persistence | 1.1.4-dev | -| | saml | 1.1.4-dev | -| | scim | 1.1.4-dev | +| | auth-server | 1.1.4 | +| | auth-server-key-rotation | 1.1.4 | +| | casa | 1.1.4 | +| | cn-istio-ingress | 1.1.4 | +| | config | 1.1.4 | +| | config-api | 1.1.4 | +| | fido2 | 1.1.4 | +| | kc-scheduler | 1.1.4 | +| | link | 1.1.4 | +| | nginx-ingress | 1.1.4 | +| | opendj | 1.1.4 | +| | persistence | 1.1.4 | +| | saml | 1.1.4 | +| | scim | 1.1.4 | ## Values | Key | Type | Default | Description | |-----|------|---------|-------------| -| auth-server | object | `{"additionalAnnotations":{},"additionalLabels":{},"customScripts":[],"dnsConfig":{},"dnsPolicy":"","hpa":{"behavior":{},"enabled":true,"maxReplicas":10,"metrics":[],"minReplicas":1,"targetCPUUtilizationPercentage":50},"image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"ghcr.io/janssenproject/jans/auth-server","tag":"1.1.4_dev"},"lifecycle":{},"livenessProbe":{"exec":{"command":["python3","/app/scripts/healthcheck.py"]},"initialDelaySeconds":30,"periodSeconds":30,"timeoutSeconds":5},"pdb":{"enabled":true,"maxUnavailable":"90%"},"readinessProbe":{"exec":{"command":["python3","/app/scripts/healthcheck.py"]},"initialDelaySeconds":25,"periodSeconds":25,"timeoutSeconds":5},"replicas":1,"resources":{"limits":{"cpu":"2500m","memory":"2500Mi"},"requests":{"cpu":"2500m","memory":"2500Mi"}},"topologySpreadConstraints":{},"usrEnvs":{"normal":{},"secret":{}},"volumeMounts":[],"volumes":[]}` | OAuth Authorization Server, the OpenID Connect Provider, the UMA Authorization Server--this is the main Internet facing component of Janssen. It's the service that returns tokens, JWT's and identity assertions. This service must be Internet facing. | -| auth-server-key-rotation | object | `{"additionalAnnotations":{},"additionalLabels":{},"customScripts":[],"dnsConfig":{},"dnsPolicy":"","image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"ghcr.io/janssenproject/jans/certmanager","tag":"1.1.4_dev"},"keysLife":48,"keysPushDelay":0,"keysPushStrategy":"NEWER","keysStrategy":"NEWER","lifecycle":{},"resources":{"limits":{"cpu":"300m","memory":"300Mi"},"requests":{"cpu":"300m","memory":"300Mi"}},"usrEnvs":{"normal":{},"secret":{}},"volumeMounts":[],"volumes":[]}` | Responsible for regenerating auth-keys per x hours | +| auth-server | object | `{"additionalAnnotations":{},"additionalLabels":{},"customScripts":[],"dnsConfig":{},"dnsPolicy":"","hpa":{"behavior":{},"enabled":true,"maxReplicas":10,"metrics":[],"minReplicas":1,"targetCPUUtilizationPercentage":50},"image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"ghcr.io/janssenproject/jans/auth-server","tag":"1.1.4-1"},"lifecycle":{},"livenessProbe":{"exec":{"command":["python3","/app/scripts/healthcheck.py"]},"initialDelaySeconds":30,"periodSeconds":30,"timeoutSeconds":5},"pdb":{"enabled":true,"maxUnavailable":"90%"},"readinessProbe":{"exec":{"command":["python3","/app/scripts/healthcheck.py"]},"initialDelaySeconds":25,"periodSeconds":25,"timeoutSeconds":5},"replicas":1,"resources":{"limits":{"cpu":"2500m","memory":"2500Mi"},"requests":{"cpu":"2500m","memory":"2500Mi"}},"topologySpreadConstraints":{},"usrEnvs":{"normal":{},"secret":{}},"volumeMounts":[],"volumes":[]}` | OAuth Authorization Server, the OpenID Connect Provider, the UMA Authorization Server--this is the main Internet facing component of Janssen. It's the service that returns tokens, JWT's and identity assertions. This service must be Internet facing. | +| auth-server-key-rotation | object | `{"additionalAnnotations":{},"additionalLabels":{},"customScripts":[],"dnsConfig":{},"dnsPolicy":"","image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"ghcr.io/janssenproject/jans/certmanager","tag":"1.1.4-1"},"keysLife":48,"keysPushDelay":0,"keysPushStrategy":"NEWER","keysStrategy":"NEWER","lifecycle":{},"resources":{"limits":{"cpu":"300m","memory":"300Mi"},"requests":{"cpu":"300m","memory":"300Mi"}},"usrEnvs":{"normal":{},"secret":{}},"volumeMounts":[],"volumes":[]}` | Responsible for regenerating auth-keys per x hours | | auth-server-key-rotation.additionalAnnotations | object | `{}` | Additional annotations that will be added across the gateway in the format of {cert-manager.io/issuer: "letsencrypt-prod"} | | auth-server-key-rotation.additionalLabels | object | `{}` | Additional labels that will be added across the gateway in the format of {mylabel: "myapp"} | | auth-server-key-rotation.customScripts | list | `[]` | Add custom scripts that have been mounted to run before the entrypoint. - /tmp/custom.sh - /tmp/custom2.sh | @@ -52,7 +52,7 @@ Kubernetes: `>=v1.22.0-0` | auth-server-key-rotation.image.pullPolicy | string | `"IfNotPresent"` | Image pullPolicy to use for deploying. | | auth-server-key-rotation.image.pullSecrets | list | `[]` | Image Pull Secrets | | auth-server-key-rotation.image.repository | string | `"ghcr.io/janssenproject/jans/certmanager"` | Image to use for deploying. | -| auth-server-key-rotation.image.tag | string | `"1.1.4_dev"` | Image tag to use for deploying. | +| auth-server-key-rotation.image.tag | string | `"1.1.4-1"` | Image tag to use for deploying. | | auth-server-key-rotation.keysLife | int | `48` | Auth server key rotation keys life in hours | | auth-server-key-rotation.keysPushDelay | int | `0` | Delay (in seconds) before pushing private keys to Auth server | | auth-server-key-rotation.keysPushStrategy | string | `"NEWER"` | Set key selection strategy after pushing private keys to Auth server (only takes effect when keysPushDelay value is greater than 0) | @@ -78,7 +78,7 @@ Kubernetes: `>=v1.22.0-0` | auth-server.image.pullPolicy | string | `"IfNotPresent"` | Image pullPolicy to use for deploying. | | auth-server.image.pullSecrets | list | `[]` | Image Pull Secrets | | auth-server.image.repository | string | `"ghcr.io/janssenproject/jans/auth-server"` | Image to use for deploying. | -| auth-server.image.tag | string | `"1.1.4_dev"` | Image tag to use for deploying. | +| auth-server.image.tag | string | `"1.1.4-1"` | Image tag to use for deploying. | | auth-server.livenessProbe | object | `{"exec":{"command":["python3","/app/scripts/healthcheck.py"]},"initialDelaySeconds":30,"periodSeconds":30,"timeoutSeconds":5}` | Configure the liveness healthcheck for the auth server if needed. | | auth-server.livenessProbe.exec | object | `{"command":["python3","/app/scripts/healthcheck.py"]}` | Executes the python3 healthcheck. https://github.com/JanssenProject/docker-jans-auth-server/blob/master/scripts/healthcheck.py | | auth-server.pdb | object | `{"enabled":true,"maxUnavailable":"90%"}` | Configure the PodDisruptionBudget | @@ -95,7 +95,7 @@ Kubernetes: `>=v1.22.0-0` | auth-server.usrEnvs.secret | object | `{}` | Add custom secret envs to the service variable1: value1 | | auth-server.volumeMounts | list | `[]` | Configure any additional volumesMounts that need to be attached to the containers | | auth-server.volumes | list | `[]` | Configure any additional volumes that need to be attached to the pod | -| casa | object | `{"additionalAnnotations":{},"additionalLabels":{},"customScripts":[],"dnsConfig":{},"dnsPolicy":"","hpa":{"behavior":{},"enabled":true,"maxReplicas":10,"metrics":[],"minReplicas":1,"targetCPUUtilizationPercentage":50},"image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"ghcr.io/janssenproject/jans/casa","tag":"1.1.4_dev"},"lifecycle":{},"livenessProbe":{"httpGet":{"path":"/jans-casa/health-check","port":"http-casa"},"initialDelaySeconds":25,"periodSeconds":25,"timeoutSeconds":5},"pdb":{"enabled":true,"maxUnavailable":"90%"},"readinessProbe":{"httpGet":{"path":"/jans-casa/health-check","port":"http-casa"},"initialDelaySeconds":30,"periodSeconds":30,"timeoutSeconds":5},"replicas":1,"resources":{"limits":{"cpu":"500m","memory":"500Mi"},"requests":{"cpu":"500m","memory":"500Mi"}},"topologySpreadConstraints":{},"usrEnvs":{"normal":{},"secret":{}},"volumeMounts":[],"volumes":[]}` | Janssen Casa ("Casa") is a self-service web portal for end-users to manage authentication and authorization preferences for their account in a Janssen Auth Server. | +| casa | object | `{"additionalAnnotations":{},"additionalLabels":{},"customScripts":[],"dnsConfig":{},"dnsPolicy":"","hpa":{"behavior":{},"enabled":true,"maxReplicas":10,"metrics":[],"minReplicas":1,"targetCPUUtilizationPercentage":50},"image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"ghcr.io/janssenproject/jans/casa","tag":"1.1.4-1"},"lifecycle":{},"livenessProbe":{"httpGet":{"path":"/jans-casa/health-check","port":"http-casa"},"initialDelaySeconds":25,"periodSeconds":25,"timeoutSeconds":5},"pdb":{"enabled":true,"maxUnavailable":"90%"},"readinessProbe":{"httpGet":{"path":"/jans-casa/health-check","port":"http-casa"},"initialDelaySeconds":30,"periodSeconds":30,"timeoutSeconds":5},"replicas":1,"resources":{"limits":{"cpu":"500m","memory":"500Mi"},"requests":{"cpu":"500m","memory":"500Mi"}},"topologySpreadConstraints":{},"usrEnvs":{"normal":{},"secret":{}},"volumeMounts":[],"volumes":[]}` | Janssen Casa ("Casa") is a self-service web portal for end-users to manage authentication and authorization preferences for their account in a Janssen Auth Server. | | casa.additionalAnnotations | object | `{}` | Additional annotations that will be added across the gateway in the format of {cert-manager.io/issuer: "letsencrypt-prod"} | | casa.additionalLabels | object | `{}` | Additional labels that will be added across the gateway in the format of {mylabel: "myapp"} | | casa.customScripts | list | `[]` | Add custom scripts that have been mounted to run before the entrypoint. - /tmp/custom.sh - /tmp/custom2.sh | @@ -107,7 +107,7 @@ Kubernetes: `>=v1.22.0-0` | casa.image.pullPolicy | string | `"IfNotPresent"` | Image pullPolicy to use for deploying. | | casa.image.pullSecrets | list | `[]` | Image Pull Secrets | | casa.image.repository | string | `"ghcr.io/janssenproject/jans/casa"` | Image to use for deploying. | -| casa.image.tag | string | `"1.1.4_dev"` | Image tag to use for deploying. | +| casa.image.tag | string | `"1.1.4-1"` | Image tag to use for deploying. | | casa.livenessProbe | object | `{"httpGet":{"path":"/jans-casa/health-check","port":"http-casa"},"initialDelaySeconds":25,"periodSeconds":25,"timeoutSeconds":5}` | Configure the liveness healthcheck for casa if needed. | | casa.livenessProbe.httpGet.path | string | `"/jans-casa/health-check"` | http liveness probe endpoint | | casa.pdb | object | `{"enabled":true,"maxUnavailable":"90%"}` | Configure the PodDisruptionBudget | @@ -125,8 +125,8 @@ Kubernetes: `>=v1.22.0-0` | casa.usrEnvs.secret | object | `{}` | Add custom secret envs to the service variable1: value1 | | casa.volumeMounts | list | `[]` | Configure any additional volumesMounts that need to be attached to the containers | | casa.volumes | list | `[]` | Configure any additional volumes that need to be attached to the pod | -| config | object | `{"additionalAnnotations":{},"additionalLabels":{},"adminPassword":"Test1234#","city":"Austin","configmap":{"cnAwsAccessKeyId":"","cnAwsDefaultRegion":"us-west-1","cnAwsProfile":"janssen","cnAwsSecretAccessKey":"","cnAwsSecretsEndpointUrl":"","cnAwsSecretsNamePrefix":"janssen","cnAwsSecretsReplicaRegions":[],"cnCacheType":"NATIVE_PERSISTENCE","cnConfigKubernetesConfigMap":"cn","cnCouchbaseBucketPrefix":"jans","cnCouchbaseCrt":"SWFtTm90YVNlcnZpY2VBY2NvdW50Q2hhbmdlTWV0b09uZQo=","cnCouchbaseIndexNumReplica":0,"cnCouchbasePassword":"P@ssw0rd","cnCouchbaseSuperUser":"admin","cnCouchbaseSuperUserPassword":"Test1234#","cnCouchbaseUrl":"cbjanssen.default.svc.cluster.local","cnCouchbaseUser":"janssen","cnGoogleProjectId":"google-project-to-save-config-and-secrets-to","cnGoogleSecretManagerServiceAccount":"SWFtTm90YVNlcnZpY2VBY2NvdW50Q2hhbmdlTWV0b09uZQo=","cnGoogleSecretNamePrefix":"janssen","cnGoogleSecretVersionId":"latest","cnGoogleSpannerDatabaseId":"","cnGoogleSpannerInstanceId":"","cnJettyRequestHeaderSize":8192,"cnLdapCrt":"SWFtTm90YVNlcnZpY2VBY2NvdW50Q2hhbmdlTWV0b09uZQo=","cnLdapKey":"SWFtTm90YVNlcnZpY2VBY2NvdW50Q2hhbmdlTWV0b09uZQo=","cnLdapUrl":"opendj:1636","cnMaxRamPercent":"75.0","cnMessageType":"DISABLED","cnOpaUrl":"http://opa.opa.svc.cluster.cluster.local:8181/v1","cnPersistenceHybridMapping":"{}","cnRedisSentinelGroup":"","cnRedisSslTruststore":"","cnRedisType":"STANDALONE","cnRedisUrl":"redis.redis.svc.cluster.local:6379","cnRedisUseSsl":false,"cnScimProtectionMode":"OAUTH","cnSecretKubernetesSecret":"cn","cnSqlDbDialect":"mysql","cnSqlDbHost":"my-release-mysql.default.svc.cluster.local","cnSqlDbName":"jans","cnSqlDbPort":3306,"cnSqlDbSchema":"","cnSqlDbTimezone":"UTC","cnSqlDbUser":"jans","cnSqldbUserPassword":"Test1234#","cnVaultAddr":"http://localhost:8200","cnVaultAppRolePath":"approle","cnVaultKvPath":"secret","cnVaultNamespace":"","cnVaultPrefix":"jans","cnVaultRoleId":"","cnVaultRoleIdFile":"/etc/certs/vault_role_id","cnVaultSecretId":"","cnVaultSecretIdFile":"/etc/certs/vault_secret_id","cnVaultVerify":false,"kcDbPassword":"Test1234#","kcDbSchema":"keycloak","kcDbUrlDatabase":"keycloak","kcDbUrlHost":"mysql.kc.svc.cluster.local","kcDbUrlPort":3306,"kcDbUrlProperties":"?useUnicode=true&characterEncoding=UTF-8&character_set_server=utf8mb4","kcDbUsername":"keycloak","kcDbVendor":"mysql","kcLogLevel":"INFO","lbAddr":"","quarkusTransactionEnableRecovery":true},"countryCode":"US","customScripts":[],"dnsConfig":{},"dnsPolicy":"","email":"support@jans.io","image":{"pullSecrets":[],"repository":"ghcr.io/janssenproject/jans/configurator","tag":"1.1.4_dev"},"ldapPassword":"P@ssw0rds","ldapTruststorePassword":"changeit","lifecycle":{},"orgName":"Janssen","redisPassword":"P@assw0rd","resources":{"limits":{"cpu":"300m","memory":"300Mi"},"requests":{"cpu":"300m","memory":"300Mi"}},"salt":"","state":"TX","usrEnvs":{"normal":{},"secret":{}},"volumeMounts":[],"volumes":[]}` | Configuration parameters for setup and initial configuration secret and config layers used by Janssen services. | -| config-api | object | `{"additionalAnnotations":{},"additionalLabels":{},"customScripts":[],"dnsConfig":{},"dnsPolicy":"","hpa":{"behavior":{},"enabled":true,"maxReplicas":10,"metrics":[],"minReplicas":1,"targetCPUUtilizationPercentage":50},"image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"ghcr.io/janssenproject/jans/config-api","tag":"1.1.4_dev"},"lifecycle":{},"livenessProbe":{"httpGet":{"path":"/jans-config-api/api/v1/health/live","port":8074},"initialDelaySeconds":30,"periodSeconds":30,"timeoutSeconds":5},"pdb":{"enabled":true,"maxUnavailable":"90%"},"readinessProbe":{"httpGet":{"path":"jans-config-api/api/v1/health/ready","port":8074},"initialDelaySeconds":25,"periodSeconds":25,"timeoutSeconds":5},"replicas":1,"resources":{"limits":{"cpu":"1000m","memory":"1200Mi"},"requests":{"cpu":"1000m","memory":"1200Mi"}},"topologySpreadConstraints":{},"usrEnvs":{"normal":{},"secret":{}},"volumeMounts":[],"volumes":[]}` | Config Api endpoints can be used to configure the auth-server, which is an open-source OpenID Connect Provider (OP) and UMA Authorization Server (AS). | +| config | object | `{"additionalAnnotations":{},"additionalLabels":{},"adminPassword":"Test1234#","city":"Austin","configmap":{"cnAwsAccessKeyId":"","cnAwsDefaultRegion":"us-west-1","cnAwsProfile":"janssen","cnAwsSecretAccessKey":"","cnAwsSecretsEndpointUrl":"","cnAwsSecretsNamePrefix":"janssen","cnAwsSecretsReplicaRegions":[],"cnCacheType":"NATIVE_PERSISTENCE","cnConfigKubernetesConfigMap":"cn","cnCouchbaseBucketPrefix":"jans","cnCouchbaseCrt":"SWFtTm90YVNlcnZpY2VBY2NvdW50Q2hhbmdlTWV0b09uZQo=","cnCouchbaseIndexNumReplica":0,"cnCouchbasePassword":"P@ssw0rd","cnCouchbaseSuperUser":"admin","cnCouchbaseSuperUserPassword":"Test1234#","cnCouchbaseUrl":"cbjanssen.default.svc.cluster.local","cnCouchbaseUser":"janssen","cnGoogleProjectId":"google-project-to-save-config-and-secrets-to","cnGoogleSecretManagerServiceAccount":"SWFtTm90YVNlcnZpY2VBY2NvdW50Q2hhbmdlTWV0b09uZQo=","cnGoogleSecretNamePrefix":"janssen","cnGoogleSecretVersionId":"latest","cnGoogleSpannerDatabaseId":"","cnGoogleSpannerInstanceId":"","cnJettyRequestHeaderSize":8192,"cnLdapCrt":"SWFtTm90YVNlcnZpY2VBY2NvdW50Q2hhbmdlTWV0b09uZQo=","cnLdapKey":"SWFtTm90YVNlcnZpY2VBY2NvdW50Q2hhbmdlTWV0b09uZQo=","cnLdapUrl":"opendj:1636","cnMaxRamPercent":"75.0","cnMessageType":"DISABLED","cnOpaUrl":"http://opa.opa.svc.cluster.cluster.local:8181/v1","cnPersistenceHybridMapping":"{}","cnRedisSentinelGroup":"","cnRedisSslTruststore":"","cnRedisType":"STANDALONE","cnRedisUrl":"redis.redis.svc.cluster.local:6379","cnRedisUseSsl":false,"cnScimProtectionMode":"OAUTH","cnSecretKubernetesSecret":"cn","cnSqlDbDialect":"mysql","cnSqlDbHost":"my-release-mysql.default.svc.cluster.local","cnSqlDbName":"jans","cnSqlDbPort":3306,"cnSqlDbSchema":"","cnSqlDbTimezone":"UTC","cnSqlDbUser":"jans","cnSqldbUserPassword":"Test1234#","cnVaultAddr":"http://localhost:8200","cnVaultAppRolePath":"approle","cnVaultKvPath":"secret","cnVaultNamespace":"","cnVaultPrefix":"jans","cnVaultRoleId":"","cnVaultRoleIdFile":"/etc/certs/vault_role_id","cnVaultSecretId":"","cnVaultSecretIdFile":"/etc/certs/vault_secret_id","cnVaultVerify":false,"kcDbPassword":"Test1234#","kcDbSchema":"keycloak","kcDbUrlDatabase":"keycloak","kcDbUrlHost":"mysql.kc.svc.cluster.local","kcDbUrlPort":3306,"kcDbUrlProperties":"?useUnicode=true&characterEncoding=UTF-8&character_set_server=utf8mb4","kcDbUsername":"keycloak","kcDbVendor":"mysql","kcLogLevel":"INFO","lbAddr":"","quarkusTransactionEnableRecovery":true},"countryCode":"US","customScripts":[],"dnsConfig":{},"dnsPolicy":"","email":"support@jans.io","image":{"pullSecrets":[],"repository":"ghcr.io/janssenproject/jans/configurator","tag":"1.1.4-1"},"ldapPassword":"P@ssw0rds","ldapTruststorePassword":"changeit","lifecycle":{},"orgName":"Janssen","redisPassword":"P@assw0rd","resources":{"limits":{"cpu":"300m","memory":"300Mi"},"requests":{"cpu":"300m","memory":"300Mi"}},"salt":"","state":"TX","usrEnvs":{"normal":{},"secret":{}},"volumeMounts":[],"volumes":[]}` | Configuration parameters for setup and initial configuration secret and config layers used by Janssen services. | +| config-api | object | `{"additionalAnnotations":{},"additionalLabels":{},"customScripts":[],"dnsConfig":{},"dnsPolicy":"","hpa":{"behavior":{},"enabled":true,"maxReplicas":10,"metrics":[],"minReplicas":1,"targetCPUUtilizationPercentage":50},"image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"ghcr.io/janssenproject/jans/config-api","tag":"1.1.4-1"},"lifecycle":{},"livenessProbe":{"httpGet":{"path":"/jans-config-api/api/v1/health/live","port":8074},"initialDelaySeconds":30,"periodSeconds":30,"timeoutSeconds":5},"pdb":{"enabled":true,"maxUnavailable":"90%"},"readinessProbe":{"httpGet":{"path":"jans-config-api/api/v1/health/ready","port":8074},"initialDelaySeconds":25,"periodSeconds":25,"timeoutSeconds":5},"replicas":1,"resources":{"limits":{"cpu":"1000m","memory":"1200Mi"},"requests":{"cpu":"1000m","memory":"1200Mi"}},"topologySpreadConstraints":{},"usrEnvs":{"normal":{},"secret":{}},"volumeMounts":[],"volumes":[]}` | Config Api endpoints can be used to configure the auth-server, which is an open-source OpenID Connect Provider (OP) and UMA Authorization Server (AS). | | config-api.additionalAnnotations | object | `{}` | Additional annotations that will be added across the gateway in the format of {cert-manager.io/issuer: "letsencrypt-prod"} | | config-api.additionalLabels | object | `{}` | Additional labels that will be added across the gateway in the format of {mylabel: "myapp"} | | config-api.customScripts | list | `[]` | Add custom scripts that have been mounted to run before the entrypoint. - /tmp/custom.sh - /tmp/custom2.sh | @@ -138,7 +138,7 @@ Kubernetes: `>=v1.22.0-0` | config-api.image.pullPolicy | string | `"IfNotPresent"` | Image pullPolicy to use for deploying. | | config-api.image.pullSecrets | list | `[]` | Image Pull Secrets | | config-api.image.repository | string | `"ghcr.io/janssenproject/jans/config-api"` | Image to use for deploying. | -| config-api.image.tag | string | `"1.1.4_dev"` | Image tag to use for deploying. | +| config-api.image.tag | string | `"1.1.4-1"` | Image tag to use for deploying. | | config-api.livenessProbe | object | `{"httpGet":{"path":"/jans-config-api/api/v1/health/live","port":8074},"initialDelaySeconds":30,"periodSeconds":30,"timeoutSeconds":5}` | Configure the liveness healthcheck for the auth server if needed. | | config-api.livenessProbe.httpGet | object | `{"path":"/jans-config-api/api/v1/health/live","port":8074}` | http liveness probe endpoint | | config-api.pdb | object | `{"enabled":true,"maxUnavailable":"90%"}` | Configure the PodDisruptionBudget | @@ -225,7 +225,7 @@ Kubernetes: `>=v1.22.0-0` | config.email | string | `"support@jans.io"` | Email address of the administrator usually. Used for certificate creation. | | config.image.pullSecrets | list | `[]` | Image Pull Secrets | | config.image.repository | string | `"ghcr.io/janssenproject/jans/configurator"` | Image to use for deploying. | -| config.image.tag | string | `"1.1.4_dev"` | Image tag to use for deploying. | +| config.image.tag | string | `"1.1.4-1"` | Image tag to use for deploying. | | config.ldapPassword | string | `"P@ssw0rds"` | LDAP admin password if OpenDJ is used for persistence. | | config.ldapTruststorePassword | string | `"changeit"` | LDAP truststore password if OpenDJ is used for persistence | | config.orgName | string | `"Janssen"` | Organization name. Used for certificate creation. | @@ -242,7 +242,7 @@ Kubernetes: `>=v1.22.0-0` | config.usrEnvs.secret | object | `{}` | Add custom secret envs to the service. variable1: value1 | | config.volumeMounts | list | `[]` | Configure any additional volumesMounts that need to be attached to the containers | | config.volumes | list | `[]` | Configure any additional volumes that need to be attached to the pod | -| fido2 | object | `{"additionalAnnotations":{},"additionalLabels":{},"customScripts":[],"dnsConfig":{},"dnsPolicy":"","hpa":{"behavior":{},"enabled":true,"maxReplicas":10,"metrics":[],"minReplicas":1,"targetCPUUtilizationPercentage":50},"image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"ghcr.io/janssenproject/jans/fido2","tag":"1.1.4_dev"},"lifecycle":{},"livenessProbe":{"httpGet":{"path":"/jans-fido2/sys/health-check","port":"http-fido2"},"initialDelaySeconds":25,"periodSeconds":25,"timeoutSeconds":5},"pdb":{"enabled":true,"maxUnavailable":"90%"},"readinessProbe":{"httpGet":{"path":"/jans-fido2/sys/health-check","port":"http-fido2"},"initialDelaySeconds":30,"periodSeconds":30,"timeoutSeconds":5},"replicas":1,"resources":{"limits":{"cpu":"500m","memory":"500Mi"},"requests":{"cpu":"500m","memory":"500Mi"}},"service":{"name":"http-fido2","port":8080},"topologySpreadConstraints":{},"usrEnvs":{"normal":{},"secret":{}},"volumeMounts":[],"volumes":[]}` | FIDO 2.0 (FIDO2) is an open authentication standard that enables leveraging common devices to authenticate to online services in both mobile and desktop environments. | +| fido2 | object | `{"additionalAnnotations":{},"additionalLabels":{},"customScripts":[],"dnsConfig":{},"dnsPolicy":"","hpa":{"behavior":{},"enabled":true,"maxReplicas":10,"metrics":[],"minReplicas":1,"targetCPUUtilizationPercentage":50},"image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"ghcr.io/janssenproject/jans/fido2","tag":"1.1.4-1"},"lifecycle":{},"livenessProbe":{"httpGet":{"path":"/jans-fido2/sys/health-check","port":"http-fido2"},"initialDelaySeconds":25,"periodSeconds":25,"timeoutSeconds":5},"pdb":{"enabled":true,"maxUnavailable":"90%"},"readinessProbe":{"httpGet":{"path":"/jans-fido2/sys/health-check","port":"http-fido2"},"initialDelaySeconds":30,"periodSeconds":30,"timeoutSeconds":5},"replicas":1,"resources":{"limits":{"cpu":"500m","memory":"500Mi"},"requests":{"cpu":"500m","memory":"500Mi"}},"service":{"name":"http-fido2","port":8080},"topologySpreadConstraints":{},"usrEnvs":{"normal":{},"secret":{}},"volumeMounts":[],"volumes":[]}` | FIDO 2.0 (FIDO2) is an open authentication standard that enables leveraging common devices to authenticate to online services in both mobile and desktop environments. | | fido2.additionalAnnotations | object | `{}` | Additional annotations that will be added across the gateway in the format of {cert-manager.io/issuer: "letsencrypt-prod"} | | fido2.additionalLabels | object | `{}` | Additional labels that will be added across the gateway in the format of {mylabel: "myapp"} | | fido2.customScripts | list | `[]` | Add custom scripts that have been mounted to run before the entrypoint. - /tmp/custom.sh - /tmp/custom2.sh | @@ -254,7 +254,7 @@ Kubernetes: `>=v1.22.0-0` | fido2.image.pullPolicy | string | `"IfNotPresent"` | Image pullPolicy to use for deploying. | | fido2.image.pullSecrets | list | `[]` | Image Pull Secrets | | fido2.image.repository | string | `"ghcr.io/janssenproject/jans/fido2"` | Image to use for deploying. | -| fido2.image.tag | string | `"1.1.4_dev"` | Image tag to use for deploying. | +| fido2.image.tag | string | `"1.1.4-1"` | Image tag to use for deploying. | | fido2.livenessProbe | object | `{"httpGet":{"path":"/jans-fido2/sys/health-check","port":"http-fido2"},"initialDelaySeconds":25,"periodSeconds":25,"timeoutSeconds":5}` | Configure the liveness healthcheck for the fido2 if needed. | | fido2.livenessProbe.httpGet | object | `{"path":"/jans-fido2/sys/health-check","port":"http-fido2"}` | http liveness probe endpoint | | fido2.pdb | object | `{"enabled":true,"maxUnavailable":"90%"}` | Configure the PodDisruptionBudget | @@ -470,7 +470,7 @@ Kubernetes: `>=v1.22.0-0` | global.usrEnvs | object | `{"normal":{},"secret":{}}` | Add custom normal and secret envs to the service. Envs defined in global.userEnvs will be globally available to all services | | global.usrEnvs.normal | object | `{}` | Add custom normal envs to the service. variable1: value1 | | global.usrEnvs.secret | object | `{}` | Add custom secret envs to the service. variable1: value1 | -| kc-scheduler | object | `{"additionalAnnotations":{},"additionalLabels":{},"customScripts":[],"dnsConfig":{},"dnsPolicy":"","image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"ghcr.io/janssenproject/jans/kc-scheduler","tag":"1.1.4_dev"},"interval":10,"lifecycle":{},"resources":{"limits":{"cpu":"300m","memory":"300Mi"},"requests":{"cpu":"300m","memory":"300Mi"}},"usrEnvs":{"normal":{},"secret":{}},"volumeMounts":[],"volumes":[]}` | Responsible for synchronizing Keycloak SAML clients | +| kc-scheduler | object | `{"additionalAnnotations":{},"additionalLabels":{},"customScripts":[],"dnsConfig":{},"dnsPolicy":"","image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"ghcr.io/janssenproject/jans/kc-scheduler","tag":"1.1.4-1"},"interval":10,"lifecycle":{},"resources":{"limits":{"cpu":"300m","memory":"300Mi"},"requests":{"cpu":"300m","memory":"300Mi"}},"usrEnvs":{"normal":{},"secret":{}},"volumeMounts":[],"volumes":[]}` | Responsible for synchronizing Keycloak SAML clients | | kc-scheduler.additionalAnnotations | object | `{}` | Additional annotations that will be added across the gateway in the format of {cert-manager.io/issuer: "letsencrypt-prod"} | | kc-scheduler.additionalLabels | object | `{}` | Additional labels that will be added across the gateway in the format of {mylabel: "myapp"} | | kc-scheduler.customScripts | list | `[]` | Add custom scripts that have been mounted to run before the entrypoint. - /tmp/custom.sh - /tmp/custom2.sh | @@ -479,7 +479,7 @@ Kubernetes: `>=v1.22.0-0` | kc-scheduler.image.pullPolicy | string | `"IfNotPresent"` | Image pullPolicy to use for deploying. | | kc-scheduler.image.pullSecrets | list | `[]` | Image Pull Secrets | | kc-scheduler.image.repository | string | `"ghcr.io/janssenproject/jans/kc-scheduler"` | Image to use for deploying. | -| kc-scheduler.image.tag | string | `"1.1.4_dev"` | Image tag to use for deploying. | +| kc-scheduler.image.tag | string | `"1.1.4-1"` | Image tag to use for deploying. | | kc-scheduler.interval | int | `10` | Interval of running the scheduler (in minutes) | | kc-scheduler.resources | object | `{"limits":{"cpu":"300m","memory":"300Mi"},"requests":{"cpu":"300m","memory":"300Mi"}}` | Resource specs. | | kc-scheduler.resources.limits.cpu | string | `"300m"` | CPU limit. | @@ -491,7 +491,7 @@ Kubernetes: `>=v1.22.0-0` | kc-scheduler.usrEnvs.secret | object | `{}` | Add custom secret envs to the service variable1: value1 | | kc-scheduler.volumeMounts | list | `[]` | Configure any additional volumesMounts that need to be attached to the containers | | kc-scheduler.volumes | list | `[]` | Configure any additional volumes that need to be attached to the pod | -| link | object | `{"additionalAnnotations":{},"additionalLabels":{},"customScripts":[],"dnsConfig":{},"dnsPolicy":"","hpa":{"behavior":{},"enabled":true,"maxReplicas":10,"metrics":[],"minReplicas":1,"targetCPUUtilizationPercentage":50},"image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"ghcr.io/janssenproject/jans/link","tag":"1.1.4_dev"},"lifecycle":{},"livenessProbe":{"exec":{"command":["python3","/app/scripts/healthcheck.py"]},"initialDelaySeconds":30,"periodSeconds":30,"timeoutSeconds":5},"pdb":{"enabled":true,"maxUnavailable":"90%"},"readinessProbe":{"exec":{"command":["python3","/app/scripts/healthcheck.py"]},"initialDelaySeconds":25,"periodSeconds":25,"timeoutSeconds":5},"replicas":1,"resources":{"limits":{"cpu":"500m","memory":"1200Mi"},"requests":{"cpu":"500m","memory":"1200Mi"}},"topologySpreadConstraints":{},"usrEnvs":{"normal":{},"secret":{}},"volumeMounts":[],"volumes":[]}` | Link. | +| link | object | `{"additionalAnnotations":{},"additionalLabels":{},"customScripts":[],"dnsConfig":{},"dnsPolicy":"","hpa":{"behavior":{},"enabled":true,"maxReplicas":10,"metrics":[],"minReplicas":1,"targetCPUUtilizationPercentage":50},"image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"ghcr.io/janssenproject/jans/link","tag":"1.1.4-1"},"lifecycle":{},"livenessProbe":{"exec":{"command":["python3","/app/scripts/healthcheck.py"]},"initialDelaySeconds":30,"periodSeconds":30,"timeoutSeconds":5},"pdb":{"enabled":true,"maxUnavailable":"90%"},"readinessProbe":{"exec":{"command":["python3","/app/scripts/healthcheck.py"]},"initialDelaySeconds":25,"periodSeconds":25,"timeoutSeconds":5},"replicas":1,"resources":{"limits":{"cpu":"500m","memory":"1200Mi"},"requests":{"cpu":"500m","memory":"1200Mi"}},"topologySpreadConstraints":{},"usrEnvs":{"normal":{},"secret":{}},"volumeMounts":[],"volumes":[]}` | Link. | | link.additionalAnnotations | object | `{}` | Additional annotations that will be added across the gateway in the format of {cert-manager.io/issuer: "letsencrypt-prod"} | | link.additionalLabels | object | `{}` | Additional labels that will be added across the gateway in the format of {mylabel: "myapp"} | | link.customScripts | list | `[]` | Add custom scripts that have been mounted to run before the entrypoint. - /tmp/custom.sh - /tmp/custom2.sh | @@ -503,7 +503,7 @@ Kubernetes: `>=v1.22.0-0` | link.image.pullPolicy | string | `"IfNotPresent"` | Image pullPolicy to use for deploying. | | link.image.pullSecrets | list | `[]` | Image Pull Secrets | | link.image.repository | string | `"ghcr.io/janssenproject/jans/link"` | Image to use for deploying. | -| link.image.tag | string | `"1.1.4_dev"` | Image tag to use for deploying. | +| link.image.tag | string | `"1.1.4-1"` | Image tag to use for deploying. | | link.livenessProbe | object | `{"exec":{"command":["python3","/app/scripts/healthcheck.py"]},"initialDelaySeconds":30,"periodSeconds":30,"timeoutSeconds":5}` | Configure the liveness healthcheck for the auth server if needed. | | link.livenessProbe.exec | object | `{"command":["python3","/app/scripts/healthcheck.py"]}` | http liveness probe endpoint | | link.pdb | object | `{"enabled":true,"maxUnavailable":"90%"}` | Configure the PodDisruptionBudget | @@ -555,7 +555,7 @@ Kubernetes: `>=v1.22.0-0` | opendj.usrEnvs.secret | object | `{}` | Add custom secret envs to the service variable1: value1 | | opendj.volumeMounts | list | `[]` | Configure any additional volumesMounts that need to be attached to the containers | | opendj.volumes | list | `[]` | Configure any additional volumes that need to be attached to the pod | -| persistence | object | `{"additionalAnnotations":{},"additionalLabels":{},"customScripts":[],"dnsConfig":{},"dnsPolicy":"","image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"ghcr.io/janssenproject/jans/persistence-loader","tag":"1.1.4_dev"},"lifecycle":{},"resources":{"limits":{"cpu":"300m","memory":"300Mi"},"requests":{"cpu":"300m","memory":"300Mi"}},"usrEnvs":{"normal":{},"secret":{}},"volumeMounts":[],"volumes":[]}` | Job to generate data and initial config for Janssen Server persistence layer. | +| persistence | object | `{"additionalAnnotations":{},"additionalLabels":{},"customScripts":[],"dnsConfig":{},"dnsPolicy":"","image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"ghcr.io/janssenproject/jans/persistence-loader","tag":"1.1.4-1"},"lifecycle":{},"resources":{"limits":{"cpu":"300m","memory":"300Mi"},"requests":{"cpu":"300m","memory":"300Mi"}},"usrEnvs":{"normal":{},"secret":{}},"volumeMounts":[],"volumes":[]}` | Job to generate data and initial config for Janssen Server persistence layer. | | persistence.additionalAnnotations | object | `{}` | Additional annotations that will be added across the gateway in the format of {cert-manager.io/issuer: "letsencrypt-prod"} | | persistence.additionalLabels | object | `{}` | Additional labels that will be added across the gateway in the format of {mylabel: "myapp"} | | persistence.customScripts | list | `[]` | Add custom scripts that have been mounted to run before the entrypoint. - /tmp/custom.sh - /tmp/custom2.sh | @@ -564,7 +564,7 @@ Kubernetes: `>=v1.22.0-0` | persistence.image.pullPolicy | string | `"IfNotPresent"` | Image pullPolicy to use for deploying. | | persistence.image.pullSecrets | list | `[]` | Image Pull Secrets | | persistence.image.repository | string | `"ghcr.io/janssenproject/jans/persistence-loader"` | Image to use for deploying. | -| persistence.image.tag | string | `"1.1.4_dev"` | Image tag to use for deploying. | +| persistence.image.tag | string | `"1.1.4-1"` | Image tag to use for deploying. | | persistence.resources | object | `{"limits":{"cpu":"300m","memory":"300Mi"},"requests":{"cpu":"300m","memory":"300Mi"}}` | Resource specs. | | persistence.resources.limits.cpu | string | `"300m"` | CPU limit | | persistence.resources.limits.memory | string | `"300Mi"` | Memory limit. | @@ -575,7 +575,7 @@ Kubernetes: `>=v1.22.0-0` | persistence.usrEnvs.secret | object | `{}` | Add custom secret envs to the service variable1: value1 | | persistence.volumeMounts | list | `[]` | Configure any additional volumesMounts that need to be attached to the containers | | persistence.volumes | list | `[]` | Configure any additional volumes that need to be attached to the pod | -| saml | object | `{"additionalAnnotations":{},"additionalLabels":{},"customScripts":[],"dnsConfig":{},"dnsPolicy":"","hpa":{"behavior":{},"enabled":true,"maxReplicas":10,"metrics":[],"minReplicas":1,"targetCPUUtilizationPercentage":50},"image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"ghcr.io/janssenproject/jans/saml","tag":"1.1.4_dev"},"lifecycle":{},"livenessProbe":{"exec":{"command":["python3","/app/scripts/healthcheck.py"]},"failureThreshold":10,"initialDelaySeconds":30,"periodSeconds":30,"timeoutSeconds":5},"pdb":{"enabled":true,"maxUnavailable":"90%"},"readinessProbe":{"exec":{"command":["python3","/app/scripts/healthcheck.py"]},"failureThreshold":10,"initialDelaySeconds":25,"periodSeconds":25,"timeoutSeconds":5},"replicas":1,"resources":{"limits":{"cpu":"500m","memory":"1200Mi"},"requests":{"cpu":"500m","memory":"1200Mi"}},"topologySpreadConstraints":{},"usrEnvs":{"normal":{},"secret":{}},"volumeMounts":[],"volumes":[]}` | SAML. | +| saml | object | `{"additionalAnnotations":{},"additionalLabels":{},"customScripts":[],"dnsConfig":{},"dnsPolicy":"","hpa":{"behavior":{},"enabled":true,"maxReplicas":10,"metrics":[],"minReplicas":1,"targetCPUUtilizationPercentage":50},"image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"ghcr.io/janssenproject/jans/saml","tag":"1.1.4-1"},"lifecycle":{},"livenessProbe":{"exec":{"command":["python3","/app/scripts/healthcheck.py"]},"failureThreshold":10,"initialDelaySeconds":30,"periodSeconds":30,"timeoutSeconds":5},"pdb":{"enabled":true,"maxUnavailable":"90%"},"readinessProbe":{"exec":{"command":["python3","/app/scripts/healthcheck.py"]},"failureThreshold":10,"initialDelaySeconds":25,"periodSeconds":25,"timeoutSeconds":5},"replicas":1,"resources":{"limits":{"cpu":"500m","memory":"1200Mi"},"requests":{"cpu":"500m","memory":"1200Mi"}},"topologySpreadConstraints":{},"usrEnvs":{"normal":{},"secret":{}},"volumeMounts":[],"volumes":[]}` | SAML. | | saml.additionalAnnotations | object | `{}` | Additional annotations that will be added across the gateway in the format of {cert-manager.io/issuer: "letsencrypt-prod"} | | saml.additionalLabels | object | `{}` | Additional labels that will be added across the gateway in the format of {mylabel: "myapp"} | | saml.customScripts | list | `[]` | Add custom scripts that have been mounted to run before the entrypoint. - /tmp/custom.sh - /tmp/custom2.sh | @@ -587,7 +587,7 @@ Kubernetes: `>=v1.22.0-0` | saml.image.pullPolicy | string | `"IfNotPresent"` | Image pullPolicy to use for deploying. | | saml.image.pullSecrets | list | `[]` | Image Pull Secrets | | saml.image.repository | string | `"ghcr.io/janssenproject/jans/saml"` | Image to use for deploying. | -| saml.image.tag | string | `"1.1.4_dev"` | Image tag to use for deploying. | +| saml.image.tag | string | `"1.1.4-1"` | Image tag to use for deploying. | | saml.livenessProbe | object | `{"exec":{"command":["python3","/app/scripts/healthcheck.py"]},"failureThreshold":10,"initialDelaySeconds":30,"periodSeconds":30,"timeoutSeconds":5}` | Configure the liveness healthcheck for the auth server if needed. | | saml.livenessProbe.exec | object | `{"command":["python3","/app/scripts/healthcheck.py"]}` | http liveness probe endpoint | | saml.pdb | object | `{"enabled":true,"maxUnavailable":"90%"}` | Configure the PodDisruptionBudget | @@ -604,7 +604,7 @@ Kubernetes: `>=v1.22.0-0` | saml.usrEnvs.secret | object | `{}` | Add custom secret envs to the service variable1: value1 | | saml.volumeMounts | list | `[]` | Configure any additional volumesMounts that need to be attached to the containers | | saml.volumes | list | `[]` | Configure any additional volumes that need to be attached to the pod | -| scim | object | `{"additionalAnnotations":{},"additionalLabels":{},"customScripts":[],"dnsConfig":{},"dnsPolicy":"","hpa":{"behavior":{},"enabled":true,"maxReplicas":10,"metrics":[],"minReplicas":1,"targetCPUUtilizationPercentage":50},"image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"ghcr.io/janssenproject/jans/scim","tag":"1.1.4_dev"},"lifecycle":{},"livenessProbe":{"httpGet":{"path":"/jans-scim/sys/health-check","port":8080},"initialDelaySeconds":30,"periodSeconds":30,"timeoutSeconds":5},"pdb":{"enabled":true,"maxUnavailable":"90%"},"readinessProbe":{"httpGet":{"path":"/jans-scim/sys/health-check","port":8080},"initialDelaySeconds":25,"periodSeconds":25,"timeoutSeconds":5},"replicas":1,"resources":{"limits":{"cpu":"1000m","memory":"1200Mi"},"requests":{"cpu":"1000m","memory":"1200Mi"}},"service":{"name":"http-scim","port":8080},"topologySpreadConstraints":{},"usrEnvs":{"normal":{},"secret":{}},"volumeMounts":[],"volumes":[]}` | System for Cross-domain Identity Management (SCIM) version 2.0 | +| scim | object | `{"additionalAnnotations":{},"additionalLabels":{},"customScripts":[],"dnsConfig":{},"dnsPolicy":"","hpa":{"behavior":{},"enabled":true,"maxReplicas":10,"metrics":[],"minReplicas":1,"targetCPUUtilizationPercentage":50},"image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"ghcr.io/janssenproject/jans/scim","tag":"1.1.4-1"},"lifecycle":{},"livenessProbe":{"httpGet":{"path":"/jans-scim/sys/health-check","port":8080},"initialDelaySeconds":30,"periodSeconds":30,"timeoutSeconds":5},"pdb":{"enabled":true,"maxUnavailable":"90%"},"readinessProbe":{"httpGet":{"path":"/jans-scim/sys/health-check","port":8080},"initialDelaySeconds":25,"periodSeconds":25,"timeoutSeconds":5},"replicas":1,"resources":{"limits":{"cpu":"1000m","memory":"1200Mi"},"requests":{"cpu":"1000m","memory":"1200Mi"}},"service":{"name":"http-scim","port":8080},"topologySpreadConstraints":{},"usrEnvs":{"normal":{},"secret":{}},"volumeMounts":[],"volumes":[]}` | System for Cross-domain Identity Management (SCIM) version 2.0 | | scim.additionalAnnotations | object | `{}` | Additional annotations that will be added across the gateway in the format of {cert-manager.io/issuer: "letsencrypt-prod"} | | scim.additionalLabels | object | `{}` | Additional labels that will be added across the gateway in the format of {mylabel: "myapp"} | | scim.customScripts | list | `[]` | Add custom scripts that have been mounted to run before the entrypoint. - /tmp/custom.sh - /tmp/custom2.sh | @@ -616,7 +616,7 @@ Kubernetes: `>=v1.22.0-0` | scim.image.pullPolicy | string | `"IfNotPresent"` | Image pullPolicy to use for deploying. | | scim.image.pullSecrets | list | `[]` | Image Pull Secrets | | scim.image.repository | string | `"ghcr.io/janssenproject/jans/scim"` | Image to use for deploying. | -| scim.image.tag | string | `"1.1.4_dev"` | Image tag to use for deploying. | +| scim.image.tag | string | `"1.1.4-1"` | Image tag to use for deploying. | | scim.livenessProbe | object | `{"httpGet":{"path":"/jans-scim/sys/health-check","port":8080},"initialDelaySeconds":30,"periodSeconds":30,"timeoutSeconds":5}` | Configure the liveness healthcheck for SCIM if needed. | | scim.livenessProbe.httpGet.path | string | `"/jans-scim/sys/health-check"` | http liveness probe endpoint | | scim.pdb | object | `{"enabled":true,"maxUnavailable":"90%"}` | Configure the PodDisruptionBudget | @@ -637,4 +637,4 @@ Kubernetes: `>=v1.22.0-0` | scim.volumes | list | `[]` | Configure any additional volumes that need to be attached to the pod | ---------------------------------------------- -Autogenerated from chart metadata using [helm-docs v1.12.0](https://github.com/norwoodj/helm-docs/releases/v1.12.0) +Autogenerated from chart metadata using [helm-docs v1.11.0](https://github.com/norwoodj/helm-docs/releases/v1.11.0) diff --git a/charts/janssen/charts/auth-server-key-rotation/Chart.yaml b/charts/janssen/charts/auth-server-key-rotation/Chart.yaml index 947907f87d0..67f114514c1 100644 --- a/charts/janssen/charts/auth-server-key-rotation/Chart.yaml +++ b/charts/janssen/charts/auth-server-key-rotation/Chart.yaml @@ -1,7 +1,7 @@ apiVersion: v2 name: auth-server-key-rotation -version: 1.1.4-dev +version: 1.1.4 kubeVersion: ">=v1.22.0-0" description: Responsible for regenerating auth-keys per x hours type: application @@ -15,4 +15,4 @@ maintainers: email: support@jans.io url: https://github.com/moabu icon: https://github.com/JanssenProject/jans/raw/main/docs/assets/logo/janssen_project_favicon_transparent_50px_50px.png -appVersion: "1.1.4-dev" \ No newline at end of file +appVersion: "1.1.4" \ No newline at end of file diff --git a/charts/janssen/charts/auth-server-key-rotation/README.md b/charts/janssen/charts/auth-server-key-rotation/README.md index f415dad66c3..202a6e2889f 100644 --- a/charts/janssen/charts/auth-server-key-rotation/README.md +++ b/charts/janssen/charts/auth-server-key-rotation/README.md @@ -1,6 +1,6 @@ # auth-server-key-rotation -![Version: 1.1.4-dev](https://img.shields.io/badge/Version-1.1.4--dev-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 1.1.4-dev](https://img.shields.io/badge/AppVersion-1.1.4--dev-informational?style=flat-square) +![Version: 1.1.4](https://img.shields.io/badge/Version-1.1.4-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 1.1.4](https://img.shields.io/badge/AppVersion-1.1.4-informational?style=flat-square) Responsible for regenerating auth-keys per x hours @@ -33,7 +33,7 @@ Kubernetes: `>=v1.22.0-0` | image.pullPolicy | string | `"IfNotPresent"` | Image pullPolicy to use for deploying. | | image.pullSecrets | list | `[]` | Image Pull Secrets | | image.repository | string | `"janssenproject/certmanager"` | Image to use for deploying. | -| image.tag | string | `"1.1.4_dev"` | Image tag to use for deploying. | +| image.tag | string | `"1.1.4-1"` | Image tag to use for deploying. | | keysLife | int | `48` | Auth server key rotation keys life in hours | | keysPushDelay | int | `0` | Delay (in seconds) before pushing private keys to Auth server | | keysPushStrategy | string | `"NEWER"` | Set key selection strategy after pushing private keys to Auth server (only takes effect when keysPushDelay value is greater than 0) | @@ -49,4 +49,4 @@ Kubernetes: `>=v1.22.0-0` | volumes | list | `[]` | Configure any additional volumes that need to be attached to the pod | ---------------------------------------------- -Autogenerated from chart metadata using [helm-docs v1.12.0](https://github.com/norwoodj/helm-docs/releases/v1.12.0) +Autogenerated from chart metadata using [helm-docs v1.11.0](https://github.com/norwoodj/helm-docs/releases/v1.11.0) diff --git a/charts/janssen/charts/auth-server-key-rotation/values.yaml b/charts/janssen/charts/auth-server-key-rotation/values.yaml index 47b984cae64..c9b204c8cce 100644 --- a/charts/janssen/charts/auth-server-key-rotation/values.yaml +++ b/charts/janssen/charts/auth-server-key-rotation/values.yaml @@ -18,7 +18,7 @@ image: # -- Image to use for deploying. repository: janssenproject/certmanager # -- Image tag to use for deploying. - tag: 1.1.4_dev + tag: 1.1.4-1 # -- Image Pull Secrets pullSecrets: [ ] # -- Auth server key rotation keys life in hours diff --git a/charts/janssen/charts/auth-server/Chart.yaml b/charts/janssen/charts/auth-server/Chart.yaml index efed1f16344..ab9a0ea1bf2 100644 --- a/charts/janssen/charts/auth-server/Chart.yaml +++ b/charts/janssen/charts/auth-server/Chart.yaml @@ -1,7 +1,7 @@ apiVersion: v2 name: auth-server -version: 1.1.4-dev +version: 1.1.4 kubeVersion: ">=v1.22.0-0" description: OAuth Authorization Server, the OpenID Connect Provider, the UMA Authorization Server--this is the main Internet facing component of Janssen. It's the service that returns tokens, JWT's and identity assertions. This service must be Internet facing. type: application @@ -17,4 +17,4 @@ maintainers: email: support@jans.io url: https://github.com/moabu icon: https://github.com/JanssenProject/jans/raw/main/docs/assets/logo/janssen_project_favicon_transparent_50px_50px.png -appVersion: "1.1.4-dev" +appVersion: "1.1.4" diff --git a/charts/janssen/charts/auth-server/README.md b/charts/janssen/charts/auth-server/README.md index 57a75598341..cd3ecd3e0c9 100644 --- a/charts/janssen/charts/auth-server/README.md +++ b/charts/janssen/charts/auth-server/README.md @@ -1,6 +1,6 @@ # auth-server -![Version: 1.1.4-dev](https://img.shields.io/badge/Version-1.1.4--dev-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 1.1.4-dev](https://img.shields.io/badge/AppVersion-1.1.4--dev-informational?style=flat-square) +![Version: 1.1.4](https://img.shields.io/badge/Version-1.1.4-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 1.1.4](https://img.shields.io/badge/AppVersion-1.1.4-informational?style=flat-square) OAuth Authorization Server, the OpenID Connect Provider, the UMA Authorization Server--this is the main Internet facing component of Janssen. It's the service that returns tokens, JWT's and identity assertions. This service must be Internet facing. @@ -36,7 +36,7 @@ Kubernetes: `>=v1.22.0-0` | image.pullPolicy | string | `"IfNotPresent"` | Image pullPolicy to use for deploying. | | image.pullSecrets | list | `[]` | Image Pull Secrets | | image.repository | string | `"janssenproject/auth-server"` | Image to use for deploying. | -| image.tag | string | `"1.1.4_dev"` | Image tag to use for deploying. | +| image.tag | string | `"1.1.4-1"` | Image tag to use for deploying. | | lifecycle | object | `{}` | | | livenessProbe | object | `{"exec":{"command":["python3","/app/scripts/healthcheck.py"]},"initialDelaySeconds":30,"periodSeconds":30,"timeoutSeconds":5}` | Configure the liveness healthcheck for the auth server if needed. | | livenessProbe.exec | object | `{"command":["python3","/app/scripts/healthcheck.py"]}` | Executes the python3 healthcheck. | @@ -58,4 +58,4 @@ Kubernetes: `>=v1.22.0-0` | volumes | list | `[]` | | ---------------------------------------------- -Autogenerated from chart metadata using [helm-docs v1.12.0](https://github.com/norwoodj/helm-docs/releases/v1.12.0) +Autogenerated from chart metadata using [helm-docs v1.11.0](https://github.com/norwoodj/helm-docs/releases/v1.11.0) diff --git a/charts/janssen/charts/auth-server/values.yaml b/charts/janssen/charts/auth-server/values.yaml index d638adac4c1..a77b0cb4c17 100644 --- a/charts/janssen/charts/auth-server/values.yaml +++ b/charts/janssen/charts/auth-server/values.yaml @@ -28,7 +28,7 @@ image: # -- Image to use for deploying. repository: janssenproject/auth-server # -- Image tag to use for deploying. - tag: 1.1.4_dev + tag: 1.1.4-1 # -- Image Pull Secrets pullSecrets: [ ] # -- Service replica number. diff --git a/charts/janssen/charts/casa/Chart.yaml b/charts/janssen/charts/casa/Chart.yaml index 735e8e969c9..0b560714592 100644 --- a/charts/janssen/charts/casa/Chart.yaml +++ b/charts/janssen/charts/casa/Chart.yaml @@ -1,6 +1,6 @@ apiVersion: v2 name: casa -version: 1.1.4-dev +version: 1.1.4 kubeVersion: ">=v1.21.0-0" description: Jans Casa ("Casa") is a self-service web portal for end-users to manage authentication and authorization preferences for their account in a Jans Server. type: application @@ -17,4 +17,4 @@ maintainers: email: support@jans.io url: https://github.com/moabu icon: https://github.com/JanssenProject/jans/raw/main/docs/assets/logo/janssen_project_favicon_transparent_50px_50px.png -appVersion: "1.1.4-dev" +appVersion: "1.1.4" diff --git a/charts/janssen/charts/casa/README.md b/charts/janssen/charts/casa/README.md index 7e443353954..b88079e9b0f 100644 --- a/charts/janssen/charts/casa/README.md +++ b/charts/janssen/charts/casa/README.md @@ -1,6 +1,6 @@ # casa -![Version: 1.1.4-dev](https://img.shields.io/badge/Version-1.1.4--dev-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 1.1.4-dev](https://img.shields.io/badge/AppVersion-1.1.4--dev-informational?style=flat-square) +![Version: 1.1.4](https://img.shields.io/badge/Version-1.1.4-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 1.1.4](https://img.shields.io/badge/AppVersion-1.1.4-informational?style=flat-square) Jans Casa ("Casa") is a self-service web portal for end-users to manage authentication and authorization preferences for their account in a Jans Server. @@ -37,7 +37,7 @@ Kubernetes: `>=v1.21.0-0` | image.pullPolicy | string | `"IfNotPresent"` | Image pullPolicy to use for deploying. | | image.pullSecrets | list | `[]` | Image Pull Secrets | | image.repository | string | `"janssenproject/casa"` | Image to use for deploying. | -| image.tag | string | `"1.1.4_dev"` | Image tag to use for deploying. | +| image.tag | string | `"1.1.4-1"` | Image tag to use for deploying. | | lifecycle | object | `{}` | | | livenessProbe | object | `{"httpGet":{"path":"/jans-casa/health-check","port":"http-casa"},"initialDelaySeconds":25,"periodSeconds":25,"timeoutSeconds":5}` | Configure the liveness healthcheck for casa if needed. | | livenessProbe.httpGet.path | string | `"/jans-casa/health-check"` | http liveness probe endpoint | @@ -63,4 +63,4 @@ Kubernetes: `>=v1.21.0-0` | volumes | list | `[]` | Configure any additional volumes that need to be attached to the pod | ---------------------------------------------- -Autogenerated from chart metadata using [helm-docs v1.12.0](https://github.com/norwoodj/helm-docs/releases/v1.12.0) +Autogenerated from chart metadata using [helm-docs v1.11.0](https://github.com/norwoodj/helm-docs/releases/v1.11.0) diff --git a/charts/janssen/charts/casa/values.yaml b/charts/janssen/charts/casa/values.yaml index 0edc507abe6..4975d45907c 100644 --- a/charts/janssen/charts/casa/values.yaml +++ b/charts/janssen/charts/casa/values.yaml @@ -27,7 +27,7 @@ image: # -- Image to use for deploying. repository: janssenproject/casa # -- Image tag to use for deploying. - tag: 1.1.4_dev + tag: 1.1.4-1 # -- Image Pull Secrets pullSecrets: [ ] # -- Service replica number. diff --git a/charts/janssen/charts/cn-istio-ingress/Chart.yaml b/charts/janssen/charts/cn-istio-ingress/Chart.yaml index 091ed8c2079..a10bea108c7 100644 --- a/charts/janssen/charts/cn-istio-ingress/Chart.yaml +++ b/charts/janssen/charts/cn-istio-ingress/Chart.yaml @@ -1,7 +1,7 @@ apiVersion: v2 name: cn-istio-ingress -version: 1.1.4-dev +version: 1.1.4 kubeVersion: ">=v1.21.0-0" description: Istio Gateway type: application @@ -17,4 +17,4 @@ maintainers: email: support@jans.io url: https://github.com/moabu icon: https://github.com/JanssenProject/jans/raw/main/docs/assets/logo/janssen_project_favicon_transparent_50px_50px.png -appVersion: "1.1.4-dev" +appVersion: "1.1.4" diff --git a/charts/janssen/charts/cn-istio-ingress/README.md b/charts/janssen/charts/cn-istio-ingress/README.md index 7301e69ac06..6b0fc070e44 100644 --- a/charts/janssen/charts/cn-istio-ingress/README.md +++ b/charts/janssen/charts/cn-istio-ingress/README.md @@ -1,6 +1,6 @@ # cn-istio-ingress -![Version: 1.1.4-dev](https://img.shields.io/badge/Version-1.1.4--dev-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 1.1.4-dev](https://img.shields.io/badge/AppVersion-1.1.4--dev-informational?style=flat-square) +![Version: 1.1.4](https://img.shields.io/badge/Version-1.1.4-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 1.1.4](https://img.shields.io/badge/AppVersion-1.1.4-informational?style=flat-square) Istio Gateway @@ -22,4 +22,4 @@ Istio Gateway Kubernetes: `>=v1.21.0-0` ---------------------------------------------- -Autogenerated from chart metadata using [helm-docs v1.12.0](https://github.com/norwoodj/helm-docs/releases/v1.12.0) +Autogenerated from chart metadata using [helm-docs v1.11.0](https://github.com/norwoodj/helm-docs/releases/v1.11.0) diff --git a/charts/janssen/charts/config-api/Chart.yaml b/charts/janssen/charts/config-api/Chart.yaml index 94150cce68c..ec2474af743 100644 --- a/charts/janssen/charts/config-api/Chart.yaml +++ b/charts/janssen/charts/config-api/Chart.yaml @@ -1,7 +1,7 @@ apiVersion: v2 name: config-api -version: 1.1.4-dev +version: 1.1.4 kubeVersion: ">=v1.22.0-0" description: Jans Config Api endpoints can be used to configure jans-auth-server, which is an open-source OpenID Connect Provider (OP) and UMA Authorization Server (AS) type: application @@ -17,4 +17,4 @@ maintainers: email: support@jans.io url: https://github.com/moabu icon: https://github.com/JanssenProject/jans/raw/main/docs/assets/logo/janssen_project_favicon_transparent_50px_50px.png -appVersion: "1.1.4-dev" +appVersion: "1.1.4" diff --git a/charts/janssen/charts/config-api/README.md b/charts/janssen/charts/config-api/README.md index e15463cce1b..8ba05cad1ec 100644 --- a/charts/janssen/charts/config-api/README.md +++ b/charts/janssen/charts/config-api/README.md @@ -1,6 +1,6 @@ # config-api -![Version: 1.1.4-dev](https://img.shields.io/badge/Version-1.1.4--dev-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 1.1.4-dev](https://img.shields.io/badge/AppVersion-1.1.4--dev-informational?style=flat-square) +![Version: 1.1.4](https://img.shields.io/badge/Version-1.1.4-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 1.1.4](https://img.shields.io/badge/AppVersion-1.1.4-informational?style=flat-square) Jans Config Api endpoints can be used to configure jans-auth-server, which is an open-source OpenID Connect Provider (OP) and UMA Authorization Server (AS) @@ -38,7 +38,7 @@ Kubernetes: `>=v1.22.0-0` | image.pullPolicy | string | `"IfNotPresent"` | Image pullPolicy to use for deploying. | | image.pullSecrets | list | `[]` | Image Pull Secrets | | image.repository | string | `"janssenproject/config-api"` | Image to use for deploying. | -| image.tag | string | `"1.1.4_dev"` | Image tag to use for deploying. | +| image.tag | string | `"1.1.4-1"` | Image tag to use for deploying. | | lifecycle | object | `{}` | | | livenessProbe | object | `{"httpGet":{"path":"/jans-config-api/api/v1/health/live","port":8074},"initialDelaySeconds":30,"periodSeconds":30,"timeoutSeconds":5}` | Configure the liveness healthcheck for the auth server if needed. | | livenessProbe.httpGet | object | `{"path":"/jans-config-api/api/v1/health/live","port":8074}` | Executes the python3 healthcheck. | @@ -62,4 +62,4 @@ Kubernetes: `>=v1.22.0-0` | volumes | list | `[]` | Configure any additional volumes that need to be attached to the pod | ---------------------------------------------- -Autogenerated from chart metadata using [helm-docs v1.12.0](https://github.com/norwoodj/helm-docs/releases/v1.12.0) +Autogenerated from chart metadata using [helm-docs v1.11.0](https://github.com/norwoodj/helm-docs/releases/v1.11.0) diff --git a/charts/janssen/charts/config-api/values.yaml b/charts/janssen/charts/config-api/values.yaml index ec6f52d60f3..d9f4249f1c0 100644 --- a/charts/janssen/charts/config-api/values.yaml +++ b/charts/janssen/charts/config-api/values.yaml @@ -31,7 +31,7 @@ image: # -- Image to use for deploying. repository: janssenproject/config-api # -- Image tag to use for deploying. - tag: 1.1.4_dev + tag: 1.1.4-1 # -- Image Pull Secrets pullSecrets: [ ] # -- Service replica number. diff --git a/charts/janssen/charts/config/Chart.yaml b/charts/janssen/charts/config/Chart.yaml index 27d2a15abb3..0114fe0d4c5 100644 --- a/charts/janssen/charts/config/Chart.yaml +++ b/charts/janssen/charts/config/Chart.yaml @@ -1,7 +1,7 @@ apiVersion: v2 name: config -version: 1.1.4-dev +version: 1.1.4 kubeVersion: ">=v1.22.0-0" description: Configuration parameters for setup and initial configuration secret and config layers used by Janssen services. type: application @@ -17,4 +17,4 @@ maintainers: email: support@jans.io url: https://github.com/moabu icon: https://github.com/JanssenProject/jans/raw/main/docs/assets/logo/janssen_project_favicon_transparent_50px_50px.png -appVersion: "1.1.4-dev" +appVersion: "1.1.4" diff --git a/charts/janssen/charts/config/README.md b/charts/janssen/charts/config/README.md index fcbf2b38405..139cca5d4fc 100644 --- a/charts/janssen/charts/config/README.md +++ b/charts/janssen/charts/config/README.md @@ -1,6 +1,6 @@ # config -![Version: 1.1.4-dev](https://img.shields.io/badge/Version-1.1.4--dev-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 1.1.4-dev](https://img.shields.io/badge/AppVersion-1.1.4--dev-informational?style=flat-square) +![Version: 1.1.4](https://img.shields.io/badge/Version-1.1.4-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 1.1.4](https://img.shields.io/badge/AppVersion-1.1.4-informational?style=flat-square) Configuration parameters for setup and initial configuration secret and config layers used by Janssen services. @@ -103,7 +103,7 @@ Kubernetes: `>=v1.22.0-0` | fullNameOverride | string | `""` | | | image.pullSecrets | list | `[]` | Image Pull Secrets | | image.repository | string | `"janssenproject/configurator"` | Image to use for deploying. | -| image.tag | string | `"1.1.4_dev"` | Image tag to use for deploying. | +| image.tag | string | `"1.1.4-1"` | Image tag to use for deploying. | | ldapPassword | string | `"P@ssw0rds"` | LDAP admin password if OpennDJ is used for persistence. | | ldapTruststorePassword | string | `"changeit"` | LDAP truststore password if OpenDJ is used for persistence | | lifecycle | object | `{}` | | @@ -128,4 +128,4 @@ Kubernetes: `>=v1.22.0-0` | volumes | list | `[]` | Configure any additional volumes that need to be attached to the pod | ---------------------------------------------- -Autogenerated from chart metadata using [helm-docs v1.12.0](https://github.com/norwoodj/helm-docs/releases/v1.12.0) +Autogenerated from chart metadata using [helm-docs v1.11.0](https://github.com/norwoodj/helm-docs/releases/v1.11.0) diff --git a/charts/janssen/charts/config/values.yaml b/charts/janssen/charts/config/values.yaml index b7f118ad1d5..19ce3459b6a 100644 --- a/charts/janssen/charts/config/values.yaml +++ b/charts/janssen/charts/config/values.yaml @@ -174,7 +174,7 @@ image: # -- Image to use for deploying. repository: janssenproject/configurator # -- Image tag to use for deploying. - tag: 1.1.4_dev + tag: 1.1.4-1 # -- Image Pull Secrets pullSecrets: [ ] # -- LDAP admin password if OpennDJ is used for persistence. diff --git a/charts/janssen/charts/fido2/Chart.yaml b/charts/janssen/charts/fido2/Chart.yaml index ebc9e5cd2be..a7715716936 100644 --- a/charts/janssen/charts/fido2/Chart.yaml +++ b/charts/janssen/charts/fido2/Chart.yaml @@ -1,7 +1,7 @@ apiVersion: v2 name: fido2 -version: 1.1.4-dev +version: 1.1.4 kubeVersion: ">=v1.22.0-0" description: FIDO 2.0 (FIDO2) is an open authentication standard that enables leveraging common devices to authenticate to online services in both mobile and desktop environments. type: application @@ -18,4 +18,4 @@ maintainers: email: support@jans.io url: https://github.com/moabu icon: https://github.com/JanssenProject/jans/raw/main/docs/assets/logo/janssen_project_favicon_transparent_50px_50px.png -appVersion: "1.1.4-dev" +appVersion: "1.1.4" diff --git a/charts/janssen/charts/fido2/README.md b/charts/janssen/charts/fido2/README.md index aee3d4f792f..d8b7a535587 100644 --- a/charts/janssen/charts/fido2/README.md +++ b/charts/janssen/charts/fido2/README.md @@ -1,6 +1,6 @@ # fido2 -![Version: 1.1.4-dev](https://img.shields.io/badge/Version-1.1.4--dev-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 1.1.4-dev](https://img.shields.io/badge/AppVersion-1.1.4--dev-informational?style=flat-square) +![Version: 1.1.4](https://img.shields.io/badge/Version-1.1.4-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 1.1.4](https://img.shields.io/badge/AppVersion-1.1.4-informational?style=flat-square) FIDO 2.0 (FIDO2) is an open authentication standard that enables leveraging common devices to authenticate to online services in both mobile and desktop environments. @@ -37,7 +37,7 @@ Kubernetes: `>=v1.22.0-0` | image.pullPolicy | string | `"IfNotPresent"` | Image pullPolicy to use for deploying. | | image.pullSecrets | list | `[]` | Image Pull Secrets | | image.repository | string | `"janssenproject/fido2"` | Image to use for deploying. | -| image.tag | string | `"1.1.4_dev"` | Image tag to use for deploying. | +| image.tag | string | `"1.1.4-1"` | Image tag to use for deploying. | | lifecycle | object | `{}` | | | livenessProbe | object | `{"httpGet":{"path":"/jans-fido2/sys/health-check","port":"http-fido2"},"initialDelaySeconds":25,"periodSeconds":25,"timeoutSeconds":5}` | Configure the liveness healthcheck for the fido2 if needed. | | livenessProbe.httpGet | object | `{"path":"/jans-fido2/sys/health-check","port":"http-fido2"}` | http liveness probe endpoint | @@ -59,4 +59,4 @@ Kubernetes: `>=v1.22.0-0` | volumes | list | `[]` | Configure any additional volumes that need to be attached to the pod | ---------------------------------------------- -Autogenerated from chart metadata using [helm-docs v1.12.0](https://github.com/norwoodj/helm-docs/releases/v1.12.0) +Autogenerated from chart metadata using [helm-docs v1.11.0](https://github.com/norwoodj/helm-docs/releases/v1.11.0) diff --git a/charts/janssen/charts/fido2/values.yaml b/charts/janssen/charts/fido2/values.yaml index aaefa7deaa9..f888b0c3f83 100644 --- a/charts/janssen/charts/fido2/values.yaml +++ b/charts/janssen/charts/fido2/values.yaml @@ -29,7 +29,7 @@ image: # -- Image to use for deploying. repository: janssenproject/fido2 # -- Image tag to use for deploying. - tag: 1.1.4_dev + tag: 1.1.4-1 # -- Image Pull Secrets pullSecrets: [ ] # -- Service replica number. diff --git a/charts/janssen/charts/kc-scheduler/Chart.yaml b/charts/janssen/charts/kc-scheduler/Chart.yaml index aceb6f234d3..fe4cf0a7de3 100644 --- a/charts/janssen/charts/kc-scheduler/Chart.yaml +++ b/charts/janssen/charts/kc-scheduler/Chart.yaml @@ -1,7 +1,7 @@ apiVersion: v2 name: kc-scheduler -version: 1.1.4-dev +version: 1.1.4 kubeVersion: ">=v1.22.0-0" description: Responsible for synchronizing Keycloak SAML clients type: application @@ -16,4 +16,4 @@ maintainers: email: support@jans.io url: https://github.com/moabu icon: https://github.com/JanssenProject/jans/raw/main/docs/assets/logo/janssen_project_favicon_transparent_50px_50px.png -appVersion: "1.1.4-dev" +appVersion: "1.1.4" diff --git a/charts/janssen/charts/kc-scheduler/README.md b/charts/janssen/charts/kc-scheduler/README.md index b7b5ab8f482..b8d2744790c 100644 --- a/charts/janssen/charts/kc-scheduler/README.md +++ b/charts/janssen/charts/kc-scheduler/README.md @@ -1,6 +1,6 @@ # kc-scheduler -![Version: 1.1.4-dev](https://img.shields.io/badge/Version-1.1.4--dev-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 1.1.4-dev](https://img.shields.io/badge/AppVersion-1.1.4--dev-informational?style=flat-square) +![Version: 1.1.4](https://img.shields.io/badge/Version-1.1.4-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 1.1.4](https://img.shields.io/badge/AppVersion-1.1.4-informational?style=flat-square) Responsible for synchronizing Keycloak SAML clients @@ -32,7 +32,7 @@ Kubernetes: `>=v1.22.0-0` | image.pullPolicy | string | `"IfNotPresent"` | Image pullPolicy to use for deploying. | | image.pullSecrets | list | `[]` | Image Pull Secrets | | image.repository | string | `"ghcr.io/janssenproject/jans/kc-scheduler"` | Image to use for deploying. | -| image.tag | string | `"1.1.4_dev"` | Image tag to use for deploying. | +| image.tag | string | `"1.1.4-1"` | Image tag to use for deploying. | | interval | int | `10` | Interval of running the scheduler (in minutes) | | lifecycle | object | `{}` | | | resources | object | `{"limits":{"cpu":"300m","memory":"300Mi"},"requests":{"cpu":"300m","memory":"300Mi"}}` | Resource specs. | @@ -47,4 +47,4 @@ Kubernetes: `>=v1.22.0-0` | volumes | list | `[]` | Configure any additional volumes that need to be attached to the pod | ---------------------------------------------- -Autogenerated from chart metadata using [helm-docs v1.12.0](https://github.com/norwoodj/helm-docs/releases/v1.12.0) +Autogenerated from chart metadata using [helm-docs v1.11.0](https://github.com/norwoodj/helm-docs/releases/v1.11.0) diff --git a/charts/janssen/charts/kc-scheduler/values.yaml b/charts/janssen/charts/kc-scheduler/values.yaml index a95753e50e1..f731b46d543 100644 --- a/charts/janssen/charts/kc-scheduler/values.yaml +++ b/charts/janssen/charts/kc-scheduler/values.yaml @@ -16,7 +16,7 @@ image: # -- Image to use for deploying. repository: ghcr.io/janssenproject/jans/kc-scheduler # -- Image tag to use for deploying. - tag: 1.1.4_dev + tag: 1.1.4-1 # -- Image Pull Secrets pullSecrets: [ ] # -- Resource specs. diff --git a/charts/janssen/charts/link/Chart.yaml b/charts/janssen/charts/link/Chart.yaml index 82487fcfedc..dfc7f4c5eaa 100644 --- a/charts/janssen/charts/link/Chart.yaml +++ b/charts/janssen/charts/link/Chart.yaml @@ -1,6 +1,6 @@ apiVersion: v2 name: link -version: 1.1.4-dev +version: 1.1.4 kubeVersion: ">=v1.22.0-0" description: Jans Link type: application @@ -15,4 +15,4 @@ maintainers: email: support@jans.io url: https://github.com/moabu icon: https://github.com/JanssenProject/jans/raw/main/docs/assets/logo/janssen_project_favicon_transparent_50px_50px.png -appVersion: "1.1.4-dev" +appVersion: "1.1.4" diff --git a/charts/janssen/charts/link/README.md b/charts/janssen/charts/link/README.md index 3f70c2ccaea..280a3353c46 100644 --- a/charts/janssen/charts/link/README.md +++ b/charts/janssen/charts/link/README.md @@ -1,6 +1,6 @@ # link -![Version: 1.1.4-dev](https://img.shields.io/badge/Version-1.1.4--dev-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 1.1.4-dev](https://img.shields.io/badge/AppVersion-1.1.4--dev-informational?style=flat-square) +![Version: 1.1.4](https://img.shields.io/badge/Version-1.1.4-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 1.1.4](https://img.shields.io/badge/AppVersion-1.1.4-informational?style=flat-square) Jans Link @@ -38,7 +38,7 @@ Kubernetes: `>=v1.22.0-0` | image.pullPolicy | string | `"IfNotPresent"` | Image pullPolicy to use for deploying. | | image.pullSecrets | list | `[]` | Image Pull Secrets | | image.repository | string | `"ghcr.io/janssenproject/jans/link"` | Image to use for deploying. | -| image.tag | string | `"1.1.4_dev"` | Image tag to use for deploying. | +| image.tag | string | `"1.1.4-1"` | Image tag to use for deploying. | | lifecycle | object | `{}` | | | livenessProbe | object | `{"exec":{"command":["python3","/app/scripts/healthcheck.py"]},"initialDelaySeconds":30,"periodSeconds":30,"timeoutSeconds":5}` | Configure the liveness healthcheck for the link if needed. | | livenessProbe.exec | object | `{"command":["python3","/app/scripts/healthcheck.py"]}` | Executes the python3 healthcheck. | @@ -62,4 +62,4 @@ Kubernetes: `>=v1.22.0-0` | volumes | list | `[]` | Configure any additional volumes that need to be attached to the pod | ---------------------------------------------- -Autogenerated from chart metadata using [helm-docs v1.12.0](https://github.com/norwoodj/helm-docs/releases/v1.12.0) +Autogenerated from chart metadata using [helm-docs v1.11.0](https://github.com/norwoodj/helm-docs/releases/v1.11.0) diff --git a/charts/janssen/charts/link/values.yaml b/charts/janssen/charts/link/values.yaml index 9465852bcbf..18fcfcebe96 100644 --- a/charts/janssen/charts/link/values.yaml +++ b/charts/janssen/charts/link/values.yaml @@ -31,7 +31,7 @@ image: # -- Image to use for deploying. repository: ghcr.io/janssenproject/jans/link # -- Image tag to use for deploying. - tag: 1.1.4_dev + tag: 1.1.4-1 # -- Image Pull Secrets pullSecrets: [ ] # -- Service replica number. diff --git a/charts/janssen/charts/nginx-ingress/Chart.yaml b/charts/janssen/charts/nginx-ingress/Chart.yaml index 46f28063bcd..bd2e433a875 100644 --- a/charts/janssen/charts/nginx-ingress/Chart.yaml +++ b/charts/janssen/charts/nginx-ingress/Chart.yaml @@ -1,7 +1,7 @@ apiVersion: v2 name: nginx-ingress -version: 1.1.4-dev +version: 1.1.4 kubeVersion: ">=v1.22.0-0" description: Nginx ingress definitions chart type: application @@ -17,4 +17,4 @@ maintainers: email: support@jans.io url: https://github.com/moabu icon: https://github.com/JanssenProject/jans/raw/main/docs/assets/logo/janssen_project_favicon_transparent_50px_50px.png -appVersion: "1.1.4-dev" +appVersion: "1.1.4" diff --git a/charts/janssen/charts/nginx-ingress/README.md b/charts/janssen/charts/nginx-ingress/README.md index 79f8168d851..8cf5bfce1d1 100644 --- a/charts/janssen/charts/nginx-ingress/README.md +++ b/charts/janssen/charts/nginx-ingress/README.md @@ -1,6 +1,6 @@ # nginx-ingress -![Version: 1.1.4-dev](https://img.shields.io/badge/Version-1.1.4--dev-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 1.1.4-dev](https://img.shields.io/badge/AppVersion-1.1.4--dev-informational?style=flat-square) +![Version: 1.1.4](https://img.shields.io/badge/Version-1.1.4-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 1.1.4](https://img.shields.io/badge/AppVersion-1.1.4-informational?style=flat-square) Nginx ingress definitions chart @@ -33,4 +33,4 @@ Kubernetes: `>=v1.22.0-0` | nameOverride | string | `""` | | ---------------------------------------------- -Autogenerated from chart metadata using [helm-docs v1.12.0](https://github.com/norwoodj/helm-docs/releases/v1.12.0) +Autogenerated from chart metadata using [helm-docs v1.11.0](https://github.com/norwoodj/helm-docs/releases/v1.11.0) diff --git a/charts/janssen/charts/opendj/Chart.yaml b/charts/janssen/charts/opendj/Chart.yaml index b8b0668d9eb..f77f5d792b5 100644 --- a/charts/janssen/charts/opendj/Chart.yaml +++ b/charts/janssen/charts/opendj/Chart.yaml @@ -1,7 +1,7 @@ apiVersion: v2 name: opendj -version: 1.1.4-dev +version: 1.1.4 kubeVersion: ">=v1.22.0-0" description: OpenDJ is a directory server which implements a wide range of Lightweight Directory Access Protocol and related standards, including full compliance with LDAPv3 but also support for Directory Service Markup Language (DSMLv2).Written in Java, OpenDJ offers multi-master replication, access control, and many extensions. type: application @@ -16,4 +16,4 @@ maintainers: email: support@jans.io url: https://github.com/moabu icon: https://github.com/JanssenProject/jans/raw/main/docs/assets/logo/janssen_project_favicon_transparent_50px_50px.png -appVersion: "1.1.4-dev" \ No newline at end of file +appVersion: "1.1.4" \ No newline at end of file diff --git a/charts/janssen/charts/opendj/README.md b/charts/janssen/charts/opendj/README.md index 7815e5cefa0..28689b035e5 100644 --- a/charts/janssen/charts/opendj/README.md +++ b/charts/janssen/charts/opendj/README.md @@ -1,6 +1,6 @@ # opendj -![Version: 1.1.4-dev](https://img.shields.io/badge/Version-1.1.4--dev-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 1.1.4-dev](https://img.shields.io/badge/AppVersion-1.1.4--dev-informational?style=flat-square) +![Version: 1.1.4](https://img.shields.io/badge/Version-1.1.4-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 1.1.4](https://img.shields.io/badge/AppVersion-1.1.4-informational?style=flat-square) OpenDJ is a directory server which implements a wide range of Lightweight Directory Access Protocol and related standards, including full compliance with LDAPv3 but also support for Directory Service Markup Language (DSMLv2).Written in Java, OpenDJ offers multi-master replication, access control, and many extensions. @@ -71,4 +71,4 @@ Kubernetes: `>=v1.22.0-0` | volumes | list | `[]` | Configure any additional volumes that need to be attached to the pod | ---------------------------------------------- -Autogenerated from chart metadata using [helm-docs v1.12.0](https://github.com/norwoodj/helm-docs/releases/v1.12.0) +Autogenerated from chart metadata using [helm-docs v1.11.0](https://github.com/norwoodj/helm-docs/releases/v1.11.0) diff --git a/charts/janssen/charts/persistence/Chart.yaml b/charts/janssen/charts/persistence/Chart.yaml index 2bbf85ef1b4..7a761a6927c 100644 --- a/charts/janssen/charts/persistence/Chart.yaml +++ b/charts/janssen/charts/persistence/Chart.yaml @@ -1,7 +1,7 @@ apiVersion: v2 name: persistence -version: 1.1.4-dev +version: 1.1.4 kubeVersion: ">=v1.22.0-0" description: Job to generate data and initial config for Janssen Server persistence layer. type: application @@ -15,5 +15,5 @@ maintainers: email: support@jans.io url: https://github.com/moabu icon: https://github.com/JanssenProject/jans/raw/main/docs/assets/logo/janssen_project_favicon_transparent_50px_50px.png -appVersion: "1.1.4-dev" +appVersion: "1.1.4" diff --git a/charts/janssen/charts/persistence/README.md b/charts/janssen/charts/persistence/README.md index 77a89eba850..b6069ecbf10 100644 --- a/charts/janssen/charts/persistence/README.md +++ b/charts/janssen/charts/persistence/README.md @@ -1,6 +1,6 @@ # persistence -![Version: 1.1.4-dev](https://img.shields.io/badge/Version-1.1.4--dev-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 1.1.4-dev](https://img.shields.io/badge/AppVersion-1.1.4--dev-informational?style=flat-square) +![Version: 1.1.4](https://img.shields.io/badge/Version-1.1.4-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 1.1.4](https://img.shields.io/badge/AppVersion-1.1.4-informational?style=flat-square) Job to generate data and initial config for Janssen Server persistence layer. @@ -33,7 +33,7 @@ Kubernetes: `>=v1.22.0-0` | image.pullPolicy | string | `"IfNotPresent"` | Image pullPolicy to use for deploying. | | image.pullSecrets | list | `[]` | Image Pull Secrets | | image.repository | string | `"janssenproject/persistence"` | Image to use for deploying. | -| image.tag | string | `"1.1.4_dev"` | Image tag to use for deploying. | +| image.tag | string | `"1.1.4-1"` | Image tag to use for deploying. | | imagePullSecrets | list | `[]` | | | lifecycle | object | `{}` | | | nameOverride | string | `""` | | @@ -49,4 +49,4 @@ Kubernetes: `>=v1.22.0-0` | volumes | list | `[]` | Configure any additional volumes that need to be attached to the pod | ---------------------------------------------- -Autogenerated from chart metadata using [helm-docs v1.12.0](https://github.com/norwoodj/helm-docs/releases/v1.12.0) +Autogenerated from chart metadata using [helm-docs v1.11.0](https://github.com/norwoodj/helm-docs/releases/v1.11.0) diff --git a/charts/janssen/charts/persistence/values.yaml b/charts/janssen/charts/persistence/values.yaml index 4591a8b4dc9..3e9ddb3399c 100644 --- a/charts/janssen/charts/persistence/values.yaml +++ b/charts/janssen/charts/persistence/values.yaml @@ -18,7 +18,7 @@ image: # -- Image to use for deploying. repository: janssenproject/persistence # -- Image tag to use for deploying. - tag: 1.1.4_dev + tag: 1.1.4-1 # -- Image Pull Secrets pullSecrets: [ ] # -- Resource specs. diff --git a/charts/janssen/charts/saml/Chart.yaml b/charts/janssen/charts/saml/Chart.yaml index 69c6321bee8..c964e49e137 100644 --- a/charts/janssen/charts/saml/Chart.yaml +++ b/charts/janssen/charts/saml/Chart.yaml @@ -1,6 +1,6 @@ apiVersion: v2 name: saml -version: 1.1.4-dev +version: 1.1.4 kubeVersion: ">=v1.21.0-0" description: Jans SAML type: application @@ -15,4 +15,4 @@ maintainers: email: support@jans.io url: https://github.com/moabu icon: https://github.com/JanssenProject/jans/raw/main/docs/assets/logo/janssen_project_favicon_transparent_50px_50px.png -appVersion: "1.1.4-dev" +appVersion: "1.1.4" diff --git a/charts/janssen/charts/saml/README.md b/charts/janssen/charts/saml/README.md index 525c73fc4cf..b258c04536e 100644 --- a/charts/janssen/charts/saml/README.md +++ b/charts/janssen/charts/saml/README.md @@ -1,6 +1,6 @@ # saml -![Version: 1.1.4-dev](https://img.shields.io/badge/Version-1.1.4--dev-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 1.1.4-dev](https://img.shields.io/badge/AppVersion-1.1.4--dev-informational?style=flat-square) +![Version: 1.1.4](https://img.shields.io/badge/Version-1.1.4-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 1.1.4](https://img.shields.io/badge/AppVersion-1.1.4-informational?style=flat-square) Jans SAML @@ -36,7 +36,7 @@ Kubernetes: `>=v1.21.0-0` | image.pullPolicy | string | `"IfNotPresent"` | Image pullPolicy to use for deploying. | | image.pullSecrets | list | `[]` | Image Pull Secrets | | image.repository | string | `"janssenproject/saml"` | Image to use for deploying. | -| image.tag | string | `"1.1.4_dev"` | Image tag to use for deploying. | +| image.tag | string | `"1.1.4-1"` | Image tag to use for deploying. | | lifecycle | object | `{}` | | | livenessProbe | object | `{"exec":{"command":["python3","/app/scripts/healthcheck.py"]},"failureThreshold":10,"initialDelaySeconds":30,"periodSeconds":30,"timeoutSeconds":5}` | Configure the liveness healthcheck for saml if needed. | | livenessProbe.exec | object | `{"command":["python3","/app/scripts/healthcheck.py"]}` | Executes the python3 healthcheck. | @@ -61,4 +61,4 @@ Kubernetes: `>=v1.21.0-0` | volumes | list | `[]` | Configure any additional volumes that need to be attached to the pod | ---------------------------------------------- -Autogenerated from chart metadata using [helm-docs v1.12.0](https://github.com/norwoodj/helm-docs/releases/v1.12.0) +Autogenerated from chart metadata using [helm-docs v1.11.0](https://github.com/norwoodj/helm-docs/releases/v1.11.0) diff --git a/charts/janssen/charts/saml/values.yaml b/charts/janssen/charts/saml/values.yaml index a3a216bec10..14a3d26d69b 100644 --- a/charts/janssen/charts/saml/values.yaml +++ b/charts/janssen/charts/saml/values.yaml @@ -27,7 +27,7 @@ image: # -- Image to use for deploying. repository: janssenproject/saml # -- Image tag to use for deploying. - tag: 1.1.4_dev + tag: 1.1.4-1 # -- Image Pull Secrets pullSecrets: [ ] # -- Service replica number. diff --git a/charts/janssen/charts/scim/Chart.yaml b/charts/janssen/charts/scim/Chart.yaml index 377dedbc4ea..ab27193246a 100644 --- a/charts/janssen/charts/scim/Chart.yaml +++ b/charts/janssen/charts/scim/Chart.yaml @@ -1,7 +1,7 @@ apiVersion: v2 name: scim -version: 1.1.4-dev +version: 1.1.4 kubeVersion: ">=v1.22.0-0" description: System for Cross-domain Identity Management (SCIM) version 2.0 type: application @@ -17,4 +17,4 @@ maintainers: email: support@jans.io url: https://github.com/moabu icon: https://github.com/JanssenProject/jans/raw/main/docs/assets/logo/janssen_project_favicon_transparent_50px_50px.png -appVersion: "1.1.4-dev" +appVersion: "1.1.4" diff --git a/charts/janssen/charts/scim/README.md b/charts/janssen/charts/scim/README.md index 39260f9fdca..21b67f49053 100644 --- a/charts/janssen/charts/scim/README.md +++ b/charts/janssen/charts/scim/README.md @@ -1,6 +1,6 @@ # scim -![Version: 1.1.4-dev](https://img.shields.io/badge/Version-1.1.4--dev-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 1.1.4-dev](https://img.shields.io/badge/AppVersion-1.1.4--dev-informational?style=flat-square) +![Version: 1.1.4](https://img.shields.io/badge/Version-1.1.4-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 1.1.4](https://img.shields.io/badge/AppVersion-1.1.4-informational?style=flat-square) System for Cross-domain Identity Management (SCIM) version 2.0 @@ -36,7 +36,7 @@ Kubernetes: `>=v1.22.0-0` | image.pullPolicy | string | `"IfNotPresent"` | Image pullPolicy to use for deploying. | | image.pullSecrets | list | `[]` | Image Pull Secrets | | image.repository | string | `"janssenproject/scim"` | Image to use for deploying. | -| image.tag | string | `"1.1.4_dev"` | Image tag to use for deploying. | +| image.tag | string | `"1.1.4-1"` | Image tag to use for deploying. | | lifecycle | object | `{}` | | | livenessProbe | object | `{"httpGet":{"path":"/jans-scim/sys/health-check","port":8080},"initialDelaySeconds":30,"periodSeconds":30,"timeoutSeconds":5}` | Configure the liveness healthcheck for SCIM if needed. | | livenessProbe.httpGet.path | string | `"/jans-scim/sys/health-check"` | http liveness probe endpoint | @@ -58,4 +58,4 @@ Kubernetes: `>=v1.22.0-0` | volumes | list | `[]` | Configure any additional volumes that need to be attached to the pod | ---------------------------------------------- -Autogenerated from chart metadata using [helm-docs v1.12.0](https://github.com/norwoodj/helm-docs/releases/v1.12.0) +Autogenerated from chart metadata using [helm-docs v1.11.0](https://github.com/norwoodj/helm-docs/releases/v1.11.0) diff --git a/charts/janssen/charts/scim/values.yaml b/charts/janssen/charts/scim/values.yaml index 1258a931f0f..ae5a9e6ef0c 100644 --- a/charts/janssen/charts/scim/values.yaml +++ b/charts/janssen/charts/scim/values.yaml @@ -28,7 +28,7 @@ image: # -- Image to use for deploying. repository: janssenproject/scim # -- Image tag to use for deploying. - tag: 1.1.4_dev + tag: 1.1.4-1 # -- Image Pull Secrets pullSecrets: [ ] # -- Service replica number. diff --git a/charts/janssen/values.yaml b/charts/janssen/values.yaml index 02c3093b739..71114f72b00 100644 --- a/charts/janssen/values.yaml +++ b/charts/janssen/values.yaml @@ -47,7 +47,7 @@ auth-server: # -- Image to use for deploying. repository: ghcr.io/janssenproject/jans/auth-server # -- Image tag to use for deploying. - tag: 1.1.4_dev + tag: 1.1.4-1 # -- Image Pull Secrets pullSecrets: [ ] # -- Service replica number. @@ -124,7 +124,7 @@ auth-server-key-rotation: # -- Image to use for deploying. repository: ghcr.io/janssenproject/jans/certmanager # -- Image tag to use for deploying. - tag: 1.1.4_dev + tag: 1.1.4-1 # -- Image Pull Secrets pullSecrets: [ ] # -- Auth server key rotation keys life in hours @@ -346,7 +346,7 @@ config: # -- Image to use for deploying. repository: ghcr.io/janssenproject/jans/configurator # -- Image tag to use for deploying. - tag: 1.1.4_dev + tag: 1.1.4-1 # -- Image Pull Secrets pullSecrets: [ ] # -- LDAP admin password if OpenDJ is used for persistence. @@ -442,7 +442,7 @@ config-api: # -- Image to use for deploying. repository: ghcr.io/janssenproject/jans/config-api # -- Image tag to use for deploying. - tag: 1.1.4_dev + tag: 1.1.4-1 # -- Image Pull Secrets pullSecrets: [ ] # -- Service replica number. @@ -545,7 +545,7 @@ fido2: # -- Image to use for deploying. repository: ghcr.io/janssenproject/jans/fido2 # -- Image tag to use for deploying. - tag: 1.1.4_dev + tag: 1.1.4-1 # -- Image Pull Secrets pullSecrets: [ ] # -- Service replica number. @@ -653,7 +653,7 @@ casa: # -- Image to use for deploying. repository: ghcr.io/janssenproject/jans/casa # -- Image tag to use for deploying. - tag: 1.1.4_dev + tag: 1.1.4-1 # -- Image Pull Secrets pullSecrets: [ ] # -- Service replica number. @@ -1430,7 +1430,7 @@ persistence: # -- Image to use for deploying. repository: ghcr.io/janssenproject/jans/persistence-loader # -- Image tag to use for deploying. - tag: 1.1.4_dev + tag: 1.1.4-1 # -- Image Pull Secrets pullSecrets: [ ] # -- Resource specs. @@ -1514,7 +1514,7 @@ scim: # -- Image to use for deploying. repository: ghcr.io/janssenproject/jans/scim # -- Image tag to use for deploying. - tag: 1.1.4_dev + tag: 1.1.4-1 # -- Image Pull Secrets pullSecrets: [ ] # -- Service replica number. @@ -1622,7 +1622,7 @@ link: # -- Image to use for deploying. repository: ghcr.io/janssenproject/jans/link # -- Image tag to use for deploying. - tag: 1.1.4_dev + tag: 1.1.4-1 # -- Image Pull Secrets pullSecrets: [ ] # -- Service replica number. @@ -1729,7 +1729,7 @@ saml: # -- Image to use for deploying. repository: ghcr.io/janssenproject/jans/saml # -- Image tag to use for deploying. - tag: 1.1.4_dev + tag: 1.1.4-1 # -- Image Pull Secrets pullSecrets: [ ] # -- Service replica number. @@ -1808,7 +1808,7 @@ kc-scheduler: # -- Image to use for deploying. repository: ghcr.io/janssenproject/jans/kc-scheduler # -- Image tag to use for deploying. - tag: 1.1.4_dev + tag: 1.1.4-1 # -- Image Pull Secrets pullSecrets: [ ] # -- Resource specs. diff --git a/demos/benchmarking/docker-jans-loadtesting-jmeter/yaml/load-test/load_test_auth_code.yaml b/demos/benchmarking/docker-jans-loadtesting-jmeter/yaml/load-test/load_test_auth_code.yaml index 06d67fb4386..b3c2ce8f446 100644 --- a/demos/benchmarking/docker-jans-loadtesting-jmeter/yaml/load-test/load_test_auth_code.yaml +++ b/demos/benchmarking/docker-jans-loadtesting-jmeter/yaml/load-test/load_test_auth_code.yaml @@ -36,7 +36,7 @@ spec: - envFrom: - configMapRef: name: load-test-authz-cm - image: ghcr.io/janssenproject/jans/loadtesting-jmeter:1.1.4_dev + image: ghcr.io/janssenproject/jans/loadtesting-jmeter:1.1.4-1 imagePullPolicy: Always name: load-test-authz resources: diff --git a/demos/benchmarking/docker-jans-loadtesting-jmeter/yaml/load-test/load_test_dcr.yaml b/demos/benchmarking/docker-jans-loadtesting-jmeter/yaml/load-test/load_test_dcr.yaml index 06d8c886330..a1500c2f301 100644 --- a/demos/benchmarking/docker-jans-loadtesting-jmeter/yaml/load-test/load_test_dcr.yaml +++ b/demos/benchmarking/docker-jans-loadtesting-jmeter/yaml/load-test/load_test_dcr.yaml @@ -34,7 +34,7 @@ spec: - envFrom: - configMapRef: name: load-test-dcr-cm - image: ghcr.io/janssenproject/jans/loadtesting-jmeter:1.0.16_dev + image: ghcr.io/janssenproject/jans/loadtesting-jmeter:1.1.4_dev imagePullPolicy: Always name: load-test-dcr resources: diff --git a/demos/benchmarking/docker-jans-loadtesting-jmeter/yaml/load-test/load_test_ropc.yaml b/demos/benchmarking/docker-jans-loadtesting-jmeter/yaml/load-test/load_test_ropc.yaml index 4106f5621c4..51e9f9a36d5 100644 --- a/demos/benchmarking/docker-jans-loadtesting-jmeter/yaml/load-test/load_test_ropc.yaml +++ b/demos/benchmarking/docker-jans-loadtesting-jmeter/yaml/load-test/load_test_ropc.yaml @@ -36,7 +36,7 @@ spec: - envFrom: - configMapRef: name: load-testing-ropc-cm - image: ghcr.io/janssenproject/jans/loadtesting-jmeter:1.1.4_dev + image: ghcr.io/janssenproject/jans/loadtesting-jmeter:1.1.4-1 imagePullPolicy: Always name: load-testing-ropc resources: diff --git a/demos/benchmarking/docker-jans-loadtesting-jmeter/yaml/load-users/load_users_couchbase_job.yaml b/demos/benchmarking/docker-jans-loadtesting-jmeter/yaml/load-users/load_users_couchbase_job.yaml index 27159dd3448..754bee74728 100644 --- a/demos/benchmarking/docker-jans-loadtesting-jmeter/yaml/load-users/load_users_couchbase_job.yaml +++ b/demos/benchmarking/docker-jans-loadtesting-jmeter/yaml/load-users/load_users_couchbase_job.yaml @@ -31,7 +31,7 @@ spec: - envFrom: - configMapRef: name: load-users-cb-cm - image: ghcr.io/janssenproject/jans/loadtesting-jmeter:1.1.4_dev + image: ghcr.io/janssenproject/jans/loadtesting-jmeter:1.1.4-1 name: load-users resources: limits: diff --git a/demos/benchmarking/docker-jans-loadtesting-jmeter/yaml/load-users/load_users_ldap_job.yaml b/demos/benchmarking/docker-jans-loadtesting-jmeter/yaml/load-users/load_users_ldap_job.yaml index c18888c8ef4..5a9aba926f3 100644 --- a/demos/benchmarking/docker-jans-loadtesting-jmeter/yaml/load-users/load_users_ldap_job.yaml +++ b/demos/benchmarking/docker-jans-loadtesting-jmeter/yaml/load-users/load_users_ldap_job.yaml @@ -31,7 +31,7 @@ spec: - envFrom: - configMapRef: name: load-users-ldap-cm - image: ghcr.io/janssenproject/jans/loadtesting-jmeter:1.1.4_dev + image: ghcr.io/janssenproject/jans/loadtesting-jmeter:1.1.4-1 name: load-users resources: limits: diff --git a/demos/benchmarking/docker-jans-loadtesting-jmeter/yaml/load-users/load_users_rdbms_job.yaml b/demos/benchmarking/docker-jans-loadtesting-jmeter/yaml/load-users/load_users_rdbms_job.yaml index 16e894bdc6d..9988198ba40 100644 --- a/demos/benchmarking/docker-jans-loadtesting-jmeter/yaml/load-users/load_users_rdbms_job.yaml +++ b/demos/benchmarking/docker-jans-loadtesting-jmeter/yaml/load-users/load_users_rdbms_job.yaml @@ -34,7 +34,7 @@ spec: - envFrom: - configMapRef: name: load-users-mysql-cm - image: ghcr.io/janssenproject/jans/loadtesting-jmeter:1.1.4_dev + image: ghcr.io/janssenproject/jans/loadtesting-jmeter:1.1.4-1 name: load-users-mysql resources: limits: diff --git a/demos/benchmarking/docker-jans-loadtesting-jmeter/yaml/load-users/load_users_spanner_job.yaml b/demos/benchmarking/docker-jans-loadtesting-jmeter/yaml/load-users/load_users_spanner_job.yaml index 3dc68b7b3c1..38ed1aab333 100644 --- a/demos/benchmarking/docker-jans-loadtesting-jmeter/yaml/load-users/load_users_spanner_job.yaml +++ b/demos/benchmarking/docker-jans-loadtesting-jmeter/yaml/load-users/load_users_spanner_job.yaml @@ -38,7 +38,7 @@ spec: - envFrom: - configMapRef: name: load-users-spanner-cm - image: ghcr.io/janssenproject/jans/loadtesting-jmeter:1.1.4_dev + image: ghcr.io/janssenproject/jans/loadtesting-jmeter:1.1.4-1 volumeMounts: - mountPath: /etc/certs/google_service_account.json name: google-sa diff --git a/demos/jans-tarp/src/static/chrome/manifest.json b/demos/jans-tarp/src/static/chrome/manifest.json index f488d112e67..8d040723564 100644 --- a/demos/jans-tarp/src/static/chrome/manifest.json +++ b/demos/jans-tarp/src/static/chrome/manifest.json @@ -3,7 +3,7 @@ "manifest_version": 3, "name": "jans-tarp", "version": "1.1.4", - "version_name": "1.1.4-dev", + "version_name": "1.1.4", "description": "Relying Party tool in form of a Chrome Extension.", "icons": { "16": "icon.png", diff --git a/docker-jans-all-in-one/Dockerfile b/docker-jans-all-in-one/Dockerfile index e75affe9f05..2b19a3ee480 100644 --- a/docker-jans-all-in-one/Dockerfile +++ b/docker-jans-all-in-one/Dockerfile @@ -58,7 +58,7 @@ RUN apk update \ # Assets sync # =========== -ENV JANS_SOURCE_VERSION=1a86124407fdd8adb9f6360c8210b7e86291212f +ENV JANS_SOURCE_VERSION=433e684ea14140098002dd7ca08ecb2d50fd2c70 # note that as we're pulling from a monorepo (with multiple project in it) # we are using partial-clone and sparse-checkout to get the assets @@ -176,7 +176,7 @@ RUN mkdir -p /opt/jans/configurator/db \ COPY app /app # CN version as env var (with suffix if any, i.e. SNAPSHOT) -ENV CN_VERSION=1.1.4-SNAPSHOT +ENV CN_VERSION=1.1.4 # set directory contains installer code that will be added to Python sys.path ENV PYTHONPATH=/app diff --git a/docker-jans-auth-server/Dockerfile b/docker-jans-auth-server/Dockerfile index 467c19aeeac..ffc25a1f555 100644 --- a/docker-jans-auth-server/Dockerfile +++ b/docker-jans-auth-server/Dockerfile @@ -50,8 +50,8 @@ RUN /opt/jython/bin/pip uninstall -y pip setuptools # Auth server # =========== -ENV CN_VERSION=1.1.4-SNAPSHOT -ENV CN_BUILD_DATE='2024-08-12 08:43' +ENV CN_VERSION=1.1.4 +ENV CN_BUILD_DATE='2024-08-19 09:32' ENV CN_SOURCE_URL=https://jenkins.jans.io/maven/io/jans/jans-auth-server/${CN_VERSION}/jans-auth-server-${CN_VERSION}.war @@ -103,7 +103,7 @@ RUN mkdir -p ${JETTY_BASE}/jans-auth/agama/fl \ /app/static/rdbm \ /app/schema -ENV JANS_SOURCE_VERSION=1a86124407fdd8adb9f6360c8210b7e86291212f +ENV JANS_SOURCE_VERSION=433e684ea14140098002dd7ca08ecb2d50fd2c70 ARG JANS_SETUP_DIR=jans-linux-setup/jans_setup # note that as we're pulling from a monorepo (with multiple project in it) diff --git a/docker-jans-casa/Dockerfile b/docker-jans-casa/Dockerfile index 25e0aa09742..005a217dd48 100644 --- a/docker-jans-casa/Dockerfile +++ b/docker-jans-casa/Dockerfile @@ -29,8 +29,8 @@ RUN wget -q https://repo1.maven.org/maven2/org/eclipse/jetty/jetty-home/${JETTY_ # Casa # ==== -ENV CN_VERSION=1.1.4-SNAPSHOT -ENV CN_BUILD_DATE='2024-08-08 08:52' +ENV CN_VERSION=1.1.4 +ENV CN_BUILD_DATE='2024-08-19 07:39' ENV CN_SOURCE_URL=https://jenkins.jans.io/maven/io/jans/casa/${CN_VERSION}/casa-${CN_VERSION}.war @@ -56,7 +56,7 @@ RUN mkdir -p ${JETTY_BASE}/jans-casa/plugins \ # Assets sync # =========== -ENV JANS_SOURCE_VERSION=e157cd4c8ff92c04e400fea29c51ae54f842a678 +ENV JANS_SOURCE_VERSION=433e684ea14140098002dd7ca08ecb2d50fd2c70 ARG JANS_SETUP_DIR=jans-linux-setup/jans_setup ARG JANS_CASA_EXTRAS_DIR=jans-casa/extras diff --git a/docker-jans-certmanager/Dockerfile b/docker-jans-certmanager/Dockerfile index 267b72b87f0..eca0e5be07a 100644 --- a/docker-jans-certmanager/Dockerfile +++ b/docker-jans-certmanager/Dockerfile @@ -14,8 +14,8 @@ RUN apk update \ # =========== # JAR files required to generate OpenID Connect keys -ENV CN_VERSION=1.1.4-SNAPSHOT -ENV CN_BUILD_DATE='2024-08-08 08:31' +ENV CN_VERSION=1.1.4 +ENV CN_BUILD_DATE='2024-08-19 09:27' ENV CN_SOURCE_URL=https://jenkins.jans.io/maven/io/jans/jans-auth-client/${CN_VERSION}/jans-auth-client-${CN_VERSION}-jar-with-dependencies.jar @@ -25,7 +25,7 @@ RUN wget -q ${CN_SOURCE_URL} -P /app/javalibs/ # Assets sync # =========== -ENV JANS_SOURCE_VERSION=e157cd4c8ff92c04e400fea29c51ae54f842a678 +ENV JANS_SOURCE_VERSION=433e684ea14140098002dd7ca08ecb2d50fd2c70 # note that as we're pulling from a monorepo (with multiple project in it) # we are using partial-clone and sparse-checkout to get the assets diff --git a/docker-jans-certmanager/README.md b/docker-jans-certmanager/README.md index 5f5200eeba6..e2960f6c500 100644 --- a/docker-jans-certmanager/README.md +++ b/docker-jans-certmanager/README.md @@ -201,7 +201,7 @@ spec: spec: containers: - name: auth-key-rotation - image: ghcr.io/janssenproject/jans/certmanager:1.1.4_dev + image: ghcr.io/janssenproject/jans/certmanager:1.1.4-1 resources: requests: memory: "300Mi" diff --git a/docker-jans-config-api/Dockerfile b/docker-jans-config-api/Dockerfile index 6d148cffa5a..2541fa88fca 100644 --- a/docker-jans-config-api/Dockerfile +++ b/docker-jans-config-api/Dockerfile @@ -40,8 +40,8 @@ RUN wget -q https://maven.jans.io/maven/io/jans/jython-installer/${JYTHON_VERSIO # Config API # ========== -ENV CN_VERSION=1.1.4-SNAPSHOT -ENV CN_BUILD_DATE='2024-08-11 08:48' +ENV CN_VERSION=1.1.4 +ENV CN_BUILD_DATE='2024-08-19 08:22' ENV CN_SOURCE_URL=https://jenkins.jans.io/maven/io/jans/jans-config-api-server/${CN_VERSION}/jans-config-api-server-${CN_VERSION}.war @@ -78,7 +78,7 @@ RUN mkdir -p ${JETTY_BASE}/jans-config-api/_plugins \ # Assets sync # =========== -ENV JANS_SOURCE_VERSION=5fd27cf7a93f56b07ac4eace225991355d7e06e9 +ENV JANS_SOURCE_VERSION=433e684ea14140098002dd7ca08ecb2d50fd2c70 ARG JANS_SETUP_DIR=jans-linux-setup/jans_setup ARG JANS_CONFIG_API_RESOURCES=jans-config-api/server/src/main/resources diff --git a/docker-jans-configurator/Dockerfile b/docker-jans-configurator/Dockerfile index 51bc1fbb335..6c4974f56fe 100644 --- a/docker-jans-configurator/Dockerfile +++ b/docker-jans-configurator/Dockerfile @@ -15,8 +15,8 @@ RUN apk update \ # JAR files required to generate OpenID Connect keys -ENV CN_VERSION=1.1.4-SNAPSHOT -ENV CN_BUILD_DATE='2024-08-08 08:31' +ENV CN_VERSION=1.1.4 +ENV CN_BUILD_DATE='2024-08-19 09:27' ENV CN_SOURCE_URL=https://jenkins.jans.io/maven/io/jans/jans-auth-client/${CN_VERSION}/jans-auth-client-${CN_VERSION}-jar-with-dependencies.jar @@ -27,7 +27,7 @@ RUN mkdir -p /opt/jans/configurator/javalibs \ # Assets sync # =========== -ENV JANS_SOURCE_VERSION=e157cd4c8ff92c04e400fea29c51ae54f842a678 +ENV JANS_SOURCE_VERSION=433e684ea14140098002dd7ca08ecb2d50fd2c70 RUN git clone --depth 500 --filter blob:none --no-checkout https://github.com/janssenproject/jans /tmp/jans \ && cd /tmp/jans \ diff --git a/docker-jans-configurator/README.md b/docker-jans-configurator/README.md index 011e3ac1589..2a1410d4d62 100644 --- a/docker-jans-configurator/README.md +++ b/docker-jans-configurator/README.md @@ -147,7 +147,7 @@ To generate initial configmaps and secrets: name: config-generate-params containers: - name: configurator-load - image: ghcr.io/janssenproject/jans/configurator:1.1.4_dev + image: ghcr.io/janssenproject/jans/configurator:1.1.4-1 volumeMounts: - mountPath: /app/db/configuration.json name: config-generate-params @@ -185,7 +185,7 @@ To restore configuration from `configuration.out.json` file: name: config-dump-params containers: - name: configurator-load - image: ghcr.io/janssenproject/jans/configurator:1.1.4_dev + image: ghcr.io/janssenproject/jans/configurator:1.1.4-1 volumeMounts: - mountPath: /app/db/configuration.out.json name: config-dump-params @@ -211,7 +211,7 @@ spec: restartPolicy: Never containers: - name: configurator-dump-job - image: ghcr.io/janssenproject/jans/configurator:1.1.4_dev + image: ghcr.io/janssenproject/jans/configurator:1.1.4-1 command: - /bin/sh - -c diff --git a/docker-jans-fido2/Dockerfile b/docker-jans-fido2/Dockerfile index 2f585b098af..452aeeb0694 100644 --- a/docker-jans-fido2/Dockerfile +++ b/docker-jans-fido2/Dockerfile @@ -41,8 +41,8 @@ RUN wget -q https://maven.jans.io/maven/io/jans/jython-installer/${JYTHON_VERSIO # ===== -ENV CN_VERSION=1.1.4-SNAPSHOT -ENV CN_BUILD_DATE='2024-08-08 08:45' +ENV CN_VERSION=1.1.4 +ENV CN_BUILD_DATE='2024-08-19 09:46' ENV CN_SOURCE_URL=https://jenkins.jans.io/maven/io/jans/jans-fido2-server/${CN_VERSION}/jans-fido2-server-${CN_VERSION}.war @@ -61,7 +61,7 @@ RUN mkdir -p ${JETTY_BASE}/jans-fido2/webapps \ # Assets sync # =========== -ENV JANS_SOURCE_VERSION=e157cd4c8ff92c04e400fea29c51ae54f842a678 +ENV JANS_SOURCE_VERSION=433e684ea14140098002dd7ca08ecb2d50fd2c70 ARG JANS_SETUP_DIR=jans-linux-setup/jans_setup # note that as we're pulling from a monorepo (with multiple project in it) diff --git a/docker-jans-kc-scheduler/Dockerfile b/docker-jans-kc-scheduler/Dockerfile index d0d293d3a88..1b1becfe647 100644 --- a/docker-jans-kc-scheduler/Dockerfile +++ b/docker-jans-kc-scheduler/Dockerfile @@ -13,7 +13,7 @@ RUN apk update \ # KC scheduler # ============ -ENV CN_VERSION=1.1.4-SNAPSHOT +ENV CN_VERSION=1.1.4 ENV CN_BUILD_DATE='2024-08-06 19:16' ENV SCHEDULER_HOME=/opt/kc-scheduler @@ -38,7 +38,7 @@ RUN wget -q https://repo1.maven.org/maven2/org/codehaus/janino/janino/3.1.9/jani # Assets sync # =========== -ENV JANS_SOURCE_VERSION=e157cd4c8ff92c04e400fea29c51ae54f842a678 +ENV JANS_SOURCE_VERSION=433e684ea14140098002dd7ca08ecb2d50fd2c70 # note that as we're pulling from a monorepo (with multiple project in it) # we are using partial-clone and sparse-checkout to get the assets diff --git a/docker-jans-keycloak-link/Dockerfile b/docker-jans-keycloak-link/Dockerfile index 95fb8b68ddb..5acf6fe9c45 100644 --- a/docker-jans-keycloak-link/Dockerfile +++ b/docker-jans-keycloak-link/Dockerfile @@ -41,8 +41,8 @@ RUN wget -q https://maven.jans.io/maven/io/jans/jython-installer/${JYTHON_VERSIO # ======= -ENV CN_VERSION=1.1.4-SNAPSHOT -ENV CN_BUILD_DATE='2024-08-08 08:52' +ENV CN_VERSION=1.1.4 +ENV CN_BUILD_DATE='2024-08-19 07:28' ENV CN_SOURCE_URL=https://jenkins.jans.io/maven/io/jans/jans-keycloak-link-server/${CN_VERSION}/jans-keycloak-link-server-${CN_VERSION}.war @@ -61,7 +61,7 @@ RUN mkdir -p ${JETTY_BASE}/jans-keycloak-link/webapps \ # Assets sync # =========== -ENV JANS_SOURCE_VERSION=e157cd4c8ff92c04e400fea29c51ae54f842a678 +ENV JANS_SOURCE_VERSION=433e684ea14140098002dd7ca08ecb2d50fd2c70 ARG JANS_SETUP_DIR=jans-linux-setup/jans_setup # note that as we're pulling from a monorepo (with multiple project in it) diff --git a/docker-jans-link/Dockerfile b/docker-jans-link/Dockerfile index fd2eff70593..7b2ccfd681a 100644 --- a/docker-jans-link/Dockerfile +++ b/docker-jans-link/Dockerfile @@ -41,8 +41,8 @@ RUN wget -q https://maven.jans.io/maven/io/jans/jython-installer/${JYTHON_VERSIO # ==== -ENV CN_VERSION=1.1.4-SNAPSHOT -ENV CN_BUILD_DATE='2024-08-08 08:42' +ENV CN_VERSION=1.1.4 +ENV CN_BUILD_DATE='2024-08-19 07:19' ENV CN_SOURCE_URL=https://jenkins.jans.io/maven/io/jans/jans-link-server/${CN_VERSION}/jans-link-server-${CN_VERSION}.war @@ -61,7 +61,7 @@ RUN mkdir -p ${JETTY_BASE}/jans-link/webapps \ # Assets sync # =========== -ENV JANS_SOURCE_VERSION=e157cd4c8ff92c04e400fea29c51ae54f842a678 +ENV JANS_SOURCE_VERSION=433e684ea14140098002dd7ca08ecb2d50fd2c70 ARG JANS_SETUP_DIR=jans-linux-setup/jans_setup # note that as we're pulling from a monorepo (with multiple project in it) diff --git a/docker-jans-monolith/Dockerfile b/docker-jans-monolith/Dockerfile index ed8c7989f53..d4b538860f9 100644 --- a/docker-jans-monolith/Dockerfile +++ b/docker-jans-monolith/Dockerfile @@ -45,7 +45,7 @@ EXPOSE 443 8080 1636 # jans-linux-setup # ===================== -ENV JANS_SOURCE_VERSION=e157cd4c8ff92c04e400fea29c51ae54f842a678 +ENV JANS_SOURCE_VERSION=433e684ea14140098002dd7ca08ecb2d50fd2c70 # cleanup RUN rm -rf /tmp/jans diff --git a/docker-jans-monolith/clean.sh b/docker-jans-monolith/clean.sh index 04b7afefbb7..b77e276d682 100644 --- a/docker-jans-monolith/clean.sh +++ b/docker-jans-monolith/clean.sh @@ -23,7 +23,7 @@ if [ -z "$INSTALLED_JANSSEN_NAME" ]; then fi if [ -z "$JANSSEN_VERSION" ]; then - JANSSEN_VERSION="1.1.4_dev" + JANSSEN_VERSION="1.1.4-1" fi if [ -z "$DATABASE_VOLUME_NAME" ]; then diff --git a/docker-jans-monolith/down.sh b/docker-jans-monolith/down.sh index 079877655c0..2e0f50205b5 100644 --- a/docker-jans-monolith/down.sh +++ b/docker-jans-monolith/down.sh @@ -23,7 +23,7 @@ if [ -z "$INSTALLED_JANSSEN_NAME" ]; then fi if [ -z "$JANSSEN_VERSION" ]; then - JANSSEN_VERSION="1.1.4_dev" + JANSSEN_VERSION="1.1.4-1" fi if [ -z "$DATABASE_VOLUME_NAME" ]; then diff --git a/docker-jans-monolith/jans-couchbase-compose.yml b/docker-jans-monolith/jans-couchbase-compose.yml index 1ee690468f7..6ec37126506 100644 --- a/docker-jans-monolith/jans-couchbase-compose.yml +++ b/docker-jans-monolith/jans-couchbase-compose.yml @@ -11,7 +11,7 @@ services: networks: - cloud_bridge jans: - image: ${JANSSEN_IMAGE:-ghcr.io/janssenproject/jans/monolith:1.1.4_dev} + image: ${JANSSEN_IMAGE:-ghcr.io/janssenproject/jans/monolith:1.1.4-1} restart: always ports: - "443:443" diff --git a/docker-jans-monolith/jans-ldap-compose.yml b/docker-jans-monolith/jans-ldap-compose.yml index 8782bd46570..24d0a42ce32 100644 --- a/docker-jans-monolith/jans-ldap-compose.yml +++ b/docker-jans-monolith/jans-ldap-compose.yml @@ -1,7 +1,7 @@ version: "3.7" services: jans: - image: ${JANSSEN_IMAGE:-ghcr.io/janssenproject/jans/monolith:1.1.4_dev} + image: ${JANSSEN_IMAGE:-ghcr.io/janssenproject/jans/monolith:1.1.4-1} restart: always ports: - "443:443" diff --git a/docker-jans-monolith/jans-mysql-compose.yml b/docker-jans-monolith/jans-mysql-compose.yml index c8b9e40687d..1cf120f480c 100644 --- a/docker-jans-monolith/jans-mysql-compose.yml +++ b/docker-jans-monolith/jans-mysql-compose.yml @@ -16,7 +16,7 @@ services: - MYSQL_PASSWORD=1t5Fin3#security - MYSQL_ROOT_PASSWORD=1t5Fin3#security jans: - image: ${JANSSEN_IMAGE:-ghcr.io/janssenproject/jans/monolith:1.1.4_dev} + image: ${JANSSEN_IMAGE:-ghcr.io/janssenproject/jans/monolith:1.1.4-1} restart: always ports: - "443:443" diff --git a/docker-jans-monolith/jans-postgres-compose.yml b/docker-jans-monolith/jans-postgres-compose.yml index 9974b463fb5..5a78671b89f 100644 --- a/docker-jans-monolith/jans-postgres-compose.yml +++ b/docker-jans-monolith/jans-postgres-compose.yml @@ -14,7 +14,7 @@ services: POSTGRES_PASSWORD: 1t5Fin3#security POSTGRES_DB: jans jans: - image: ${JANSSEN_IMAGE:-ghcr.io/janssenproject/jans/monolith:1.1.4_dev} + image: ${JANSSEN_IMAGE:-ghcr.io/janssenproject/jans/monolith:1.1.4-1} restart: always ports: - "443:443" diff --git a/docker-jans-monolith/jans-spanner-compose.yml b/docker-jans-monolith/jans-spanner-compose.yml index 26ea5569c50..06cef3a5cc7 100644 --- a/docker-jans-monolith/jans-spanner-compose.yml +++ b/docker-jans-monolith/jans-spanner-compose.yml @@ -1,7 +1,7 @@ version: "3.7" services: jans: - image: ${JANSSEN_IMAGE:-ghcr.io/janssenproject/jans/monolith:1.1.4_dev} + image: ${JANSSEN_IMAGE:-ghcr.io/janssenproject/jans/monolith:1.1.4-1} restart: always ports: - "443:443" diff --git a/docker-jans-monolith/up.sh b/docker-jans-monolith/up.sh index c071b29cf32..2565e3f28f2 100644 --- a/docker-jans-monolith/up.sh +++ b/docker-jans-monolith/up.sh @@ -23,7 +23,7 @@ if [ -z "$INSTALLED_JANSSEN_NAME" ]; then fi if [ -z "$JANSSEN_VERSION" ]; then - JANSSEN_VERSION="1.1.4_dev" + JANSSEN_VERSION="1.1.4-1" fi if [ -z "$DATABASE_VOLUME_NAME" ]; then diff --git a/docker-jans-persistence-loader/Dockerfile b/docker-jans-persistence-loader/Dockerfile index 5c2ef2308ba..aabaf016b48 100644 --- a/docker-jans-persistence-loader/Dockerfile +++ b/docker-jans-persistence-loader/Dockerfile @@ -16,7 +16,7 @@ RUN apk update \ # =========== # janssenproject/jans SHA commit -ENV JANS_SOURCE_VERSION=1a86124407fdd8adb9f6360c8210b7e86291212f +ENV JANS_SOURCE_VERSION=433e684ea14140098002dd7ca08ecb2d50fd2c70 ARG JANS_SETUP_DIR=jans-linux-setup/jans_setup ARG JANS_SCRIPT_CATALOG_DIR=docs/script-catalog ARG JANS_CONFIG_API_RESOURCES=jans-config-api/server/src/main/resources diff --git a/docker-jans-saml/Dockerfile b/docker-jans-saml/Dockerfile index c1b79262f8c..9e1a67d5aa8 100644 --- a/docker-jans-saml/Dockerfile +++ b/docker-jans-saml/Dockerfile @@ -23,7 +23,7 @@ RUN mkdir -p /opt/keycloak/logs \ # KC integration # ============== -ENV CN_VERSION=1.1.4-SNAPSHOT +ENV CN_VERSION=1.1.4 ENV CN_BUILD_DATE='2024-08-06 19:16' RUN wget -q https://jenkins.jans.io/maven/io/jans/kc-jans-spi/${CN_VERSION}/kc-jans-spi-${CN_VERSION}.jar -P /opt/keycloak/providers \ @@ -35,7 +35,7 @@ RUN wget -q https://jenkins.jans.io/maven/io/jans/kc-jans-spi/${CN_VERSION}/kc-j # Assets sync # =========== -ENV JANS_SOURCE_VERSION=e157cd4c8ff92c04e400fea29c51ae54f842a678 +ENV JANS_SOURCE_VERSION=433e684ea14140098002dd7ca08ecb2d50fd2c70 ARG JANS_SETUP_DIR=jans-linux-setup/jans_setup # note that as we're pulling from a monorepo (with multiple project in it) diff --git a/docker-jans-scim/Dockerfile b/docker-jans-scim/Dockerfile index 0c74ba4a955..64971632f47 100644 --- a/docker-jans-scim/Dockerfile +++ b/docker-jans-scim/Dockerfile @@ -40,8 +40,8 @@ RUN wget -q https://maven.jans.io/maven/io/jans/jython-installer/${JYTHON_VERSIO # SCIM # ==== -ENV CN_VERSION=1.1.4-SNAPSHOT -ENV CN_BUILD_DATE='2024-08-08 08:49' +ENV CN_VERSION=1.1.4 +ENV CN_BUILD_DATE='2024-08-19 08:17' ENV CN_SOURCE_URL=https://jenkins.jans.io/maven/io/jans/jans-scim-server/${CN_VERSION}/jans-scim-server-${CN_VERSION}.war @@ -60,7 +60,7 @@ RUN mkdir -p ${JETTY_BASE}/jans-scim/webapps \ # Assets sync # =========== -ENV JANS_SOURCE_VERSION=e157cd4c8ff92c04e400fea29c51ae54f842a678 +ENV JANS_SOURCE_VERSION=433e684ea14140098002dd7ca08ecb2d50fd2c70 ARG JANS_SETUP_DIR=jans-linux-setup/jans_setup ARG JANS_SCIM_RESOURCE_DIR=jans-scim/server/src/main/resources diff --git a/docs/admin/README.md b/docs/admin/README.md index 620fe3270e6..4baa703d22f 100644 --- a/docs/admin/README.md +++ b/docs/admin/README.md @@ -13,12 +13,12 @@ each specific area. * **Deployment and Planning Guide** High level design concepts and architecture. -* **Installation** Howto's for VM and cloud native deployment +* **Installation** Howto's for VM and cloud-native deployment -* **Kubernetes Operation Guide** Day-to-day administration for cloud native +* **Kubernetes Operation Guide** Day-to-day administration for cloud-native * **VM Operation Guide** Day-to-day administration if you installed a SUSE, -Red Hat, or Ubuntu linux package. +Red Hat, or Ubuntu Linux package. * **Configuration Guide** How to use the various configuration tools: command line, `curl`, or the text user interface ("TUI"). diff --git a/docs/admin/developer/agama/flows-navigation-ui.md b/docs/admin/developer/agama/flows-navigation-ui.md index e177d5e2b6c..5c490c92e6f 100644 --- a/docs/admin/developer/agama/flows-navigation-ui.md +++ b/docs/admin/developer/agama/flows-navigation-ui.md @@ -71,12 +71,14 @@ And here the UI page contents: ### Extended data model -The data model (injected _map_) is attached a couple of additional keys for developer's convenience: +The data model (injected _map_) is attached some additional keys for convenience: - `webCtx`. It gives easy access to often needed bits like current path, locale, etc. This is a Java object you can inspect [here](https://github.com/JanssenProject/jans/blob/main/jans-auth-server/agama/engine/src/main/java/io/jans/agama/engine/service/WebContext.java). Take a look at the getters; writing `${webCtx.contextPath}` in a template will insert the result of calling method `getContextPath` - normally the string `/jans-auth`. - `msgs`. It gives access to the localized messages of jans-auth application. Some developers might know this as the "internationalization labels" or "resource bundle" of an application. This is a collection of `.properties` files where common UI-related messages in different languages can be found. A message (label) is identified by a key, so in a template `${msgs.}` could be used. As most keys in resource bundles have dot characters, the alternative notation `${webCtx["KEY"]}` works better for FreeMarker, for example `${msgs["login.errorMessage"]}`. +- `cache`. Allows developers to retrieve values already stored in the Jans configured cache, e.g. `${cache.myKey}`. To avoid template errors in case of a cache miss, you can use Freemarker's safeguard [expressions](https://freemarker.apache.org/docs/dgui_template_exp.html#dgui_template_exp_missing). Note you cannot store/modify values in the cache from templates. + ### Assets handling Clearly, templates can link other local web resources like Javascript code, images, etc. The location of this kind of files is expected to be in the filesystem under `/fl` directory. Note this is not the same directory of templates. Doing so would allow users to retrieve the code of templates by simple URL manipulation. diff --git a/docs/admin/lock/lock-server.md b/docs/admin/lock/lock-server.md index 0160f9410ed..3a655855f67 100644 --- a/docs/admin/lock/lock-server.md +++ b/docs/admin/lock/lock-server.md @@ -11,7 +11,7 @@ tags: # Jans Lock Overview Lock Server is a Java Weld application that connects ephemeral Cedarlings to the enterprise by -providing a number of [endpoints](https://gluu.org/swagger-ui/?url=https://raw.githubusercontent.com/JanssenProject/jans/main/jans-lock/lock-master.yaml) +providing a number of [endpoints](https://gluu.org/swagger-ui/?url=https://raw.githubusercontent.com/JanssenProject/jans/main/jans-lock/lock-server.yaml) ## Installation diff --git a/docs/admin/planning/README.md b/docs/admin/planning/README.md index 48d75b615b1..8ece0595d26 100644 --- a/docs/admin/planning/README.md +++ b/docs/admin/planning/README.md @@ -7,7 +7,7 @@ tags: # Overview -This Deployment Guide will help you to plan how to launch a digital identity +This Deployment Guide will help you plan how to launch a digital identity service for your organization. It will hopefully answer many of the "why" questions, not just the "how" questions, setting the stage for what challenges are in scope for Janssen--and where you may need to use other software. It @@ -18,7 +18,7 @@ By covering the key features and designs, hopefully, this guide will help you un to right-size your Janssen identity services. The audience for this deployment guide includes technical architects, designers, -developers and Janssen administrators. +developers, and Janssen administrators. !!! Contribute If you’d like to contribute to this document, get started with the [Contribution Guide](https://docs.jans.io/head/CONTRIBUTING/#contributing-to-the-documentation) diff --git a/docs/admin/planning/application-portal.md b/docs/admin/planning/application-portal.md index ae7a3d1ca82..c332b4a1d97 100644 --- a/docs/admin/planning/application-portal.md +++ b/docs/admin/planning/application-portal.md @@ -5,7 +5,7 @@ tags: - portal --- -An application portal ("portal") is a website which displays all the +An application portal ("portal") is a website that displays all the protected applications available for an end user to access. The Janssen Project does not provide a portal. But you can build your own. diff --git a/docs/admin/planning/benchmarking.md b/docs/admin/planning/benchmarking.md index c600025c62b..af945f16dd8 100644 --- a/docs/admin/planning/benchmarking.md +++ b/docs/admin/planning/benchmarking.md @@ -8,13 +8,13 @@ tags: Want confidence that your Janssen platform will perform with the latency and concurrency you need in production? If so, then you MUST benchmark properly. It's critical that your test data and transactions mock what you need to prove -in production. For cloud native deployments, benchmarking is also essential +in production. For cloud-native deployments, benchmarking is also essential to test auto-scaling and failover. Ideally, you'll test the same hardware and network. Remember that OAuth has different flows, which have a different number of steps, and different requirements for compute and persistence. For example, the -OAuth Client Credential Grant is very short: there is one token request, and +OAuth Client Credential Grant is very short: there is one token request and one token response. The OpenID Code Flow has many more steps: it has a request/response to the authorization, token, Userinfo and logout endpoints. It's really important to test the exact flow you intend to use in production. @@ -22,40 +22,40 @@ It's really important to test the exact flow you intend to use in production. Benchmarking also has the benefit of testing the index configuration in your database. Every database trades disk space for performance by using indexes. If you miss an index, performance sometimes comes to a grinding halt. Your -service may even crash. Having confidence that all potential index scenario's +service may even crash. Having confidence that all potential index scenarios get executed in your benchmarking is essential. Auth Server publishes [JUnit](https://junit.org) tests and some tools for generating test data. Because each page rendered by Auth Server has a state, you cannot use a static load generation page tool. Don't forget to gather data -on compute, storage, and memory. Also watch the resources consumed by the each +on compute, storage, and memory. Also, watch the resources consumed by each web service and system service (e.g. database). You can't find the bottleneck without this data. System libraries and hardware choices may also impact your results. Benchmarking is an iterative process. Inevitably, things never go exactly how you guessed they would. And you make changes to your environment and run the -benchmarking tests again--*ad naseum*. Leave enough time for benchmarking. How -ever much time you think it will take, triple your estimate. +benchmarking tests again--*ad nauseam*. Leave enough time for benchmarking. However +much time you think it will take, triple your estimate. Make sure you look at both short tests and long running tests. A slow memory leak may only present after many hours of high load. Also, run some crazy tests, -just so you know what happens. Some organizations benchmark for ten times -normal volume. But when an incident happens, they see 1,000 times normal volume. +just so you know what happens. Some organizations benchmark for ten times the +normal volume. But when an incident happens, they see 1,000 times the normal volume. Think outside-the-box. It's tricky load testing some newer two-factor authentication services, especially if they rely on new features of the browser. Hopefully the tools to benchmark these will evolve. -Janssen Auth Server supports a number of deployment models--both VM and cloud -native. While cloud native architecture enables true horizontal scalability, +Janssen Auth Server supports a number of deployment models--both VM and cloud-native. +While cloud-native architecture enables true horizontal scalability, it comes at a cost. Benchmarking can help you understand if that cost is justified. ## Load test -In cloud native architecture, the load testing is executed via k8s pods. +In cloud-native architecture, the load testing is executed via k8s pods. ### Authorization Code Flow jmeter load test diff --git a/docs/admin/planning/caching.md b/docs/admin/planning/caching.md index 65c029cdcc3..fd162f1fbea 100644 --- a/docs/admin/planning/caching.md +++ b/docs/admin/planning/caching.md @@ -35,5 +35,5 @@ supports TLS, which is a good option if you need secure communication. run for other applications. We have observed a slightly higher cache miss rate under high load, which is fairly atypical for most login applications. -1. **Cloud Cache** Amazon ElastiCache or Google Memorystore offer both Redis +1. **Cloud Cache** Amazon ElastiCache or Google Memorystore offers both Redis and Memcached managed services. They work fine. diff --git a/docs/admin/planning/central-auth-service.md b/docs/admin/planning/central-auth-service.md index 387b776d109..3e9425aa8a3 100644 --- a/docs/admin/planning/central-auth-service.md +++ b/docs/admin/planning/central-auth-service.md @@ -5,7 +5,7 @@ tags: - integration --- -Older monolithic web access management platforms from the 2000's had +Older monolithic web access management platforms from the 2000s had features to allow central policy management--what users can access what resources. But modern federated digital identity platforms generally do not. That's true for two reasons. First implementing all the OAuth and OpenID diff --git a/docs/admin/planning/certificates-keys.md b/docs/admin/planning/certificates-keys.md index 295ddf51d3e..32b79c40015 100644 --- a/docs/admin/planning/certificates-keys.md +++ b/docs/admin/planning/certificates-keys.md @@ -15,7 +15,7 @@ tags: Janssen uses keys for signing and encryption, primarily concerning JSON documents. There are six IETF RFCs that provide considerable detail: -* [RFC 7515 JSON Web Signing (JWE)](https://www.rfc-editor.org/rfc/rfc7515) +* [RFC 7515 JSON Web Signing (JWS)](https://www.rfc-editor.org/rfc/rfc7515) * [RFC 7516 JSON Web Encryption (JWE)](https://www.rfc-editor.org/rfc/rfc7516) * [RFC 7517 JSON Web Key (JWK)](https://www.rfc-editor.org/rfc/rfc7517) * [RFC 7518 JSON Web Algorithms (JWA)](https://www.rfc-editor.org/rfc/rfc7518) diff --git a/docs/admin/planning/components.md b/docs/admin/planning/components.md index 4f53fc612fe..383666ff203 100644 --- a/docs/admin/planning/components.md +++ b/docs/admin/planning/components.md @@ -11,9 +11,9 @@ deployment. 1. **Auth Server**: This component is the OAuth Authorization Server, the OpenID -Connect Provider, the UMA Authorization Server--this is the main Internet facing -component of Janssen. It's the service that returns tokens, JWT's and identity -assertions. This service must be Internet facing. +Connect Provider, and the UMA Authorization Server--this is the main Internet-facing +component of Janssen. It's the service that returns tokens, JWTs, and identity +assertions. This service must be Internet-facing. 1. **Database**: Like most IAM platforms, Janssen requires some kind of persistence service to store configuration and other entity data (client, @@ -25,10 +25,10 @@ databases may be added in the future. 1. **Cache**: Getting data from a disk is still the slowest part of any web platform. If you want higher transaction speeds, one strategy is to use a memory cache instead of the disk (i.e. database). Janssen was designed -to store short lived objects in the cache, like the `code` in the OpenID code +to store short-lived objects in the cache, like the `code` in the OpenID code flow (which is only used one time) or access tokens, which only live for a few -minutes. Currently Janssen has three options for cache: `in-memory`, which is -suitable only for one node VM deploymetns; `redis` which is probably your best +minutes. Currently, Janssen has three options for cache: `in-memory`, which is +suitable only for one node VM deployments; `redis` which is probably your best option; and `memcached` which you should use if a Redis cache service is not available (and tends to have more cache misses under high volume). @@ -56,15 +56,15 @@ the OAuth Device flow. The CLI need not be on the same server as any of the components (you can run it from your desktop). But you will need network connectivity to the Config API and the Auth Server. -1. **TUI**: An menu-driven interactive tool for configuration, the "TUI" or -"text user interface" might resemble an 90's BIOS configuration, but it gets +1. **TUI**: A menu-driven interactive tool for configuration, the "TUI" or +"text user interface" might resemble a 90's BIOS configuration, but it gets the job done without the need for a web browser. Like the CLI, you can run it from anywhere, but need connectivity to the Config API and Auth Server. -The TUI writes a "CLI log"--the one liner you could have executed to do whatever +The TUI writes a "CLI log"--the one-liner you could have executed to do whatever you just did in the interface. This will help you if you want to script stuff later on. -1. **Jans Core**: This library has code that is shared across several janssen +1. **Jans Core**: This library has code that is shared across several Janssen projects. You will most likely need this project when you build other Janssen components. @@ -77,5 +77,5 @@ language) designed for the sole purpose of writing web flows. 1. **Setup**: Configuring a Janssen Auth Server platform is complicated. How do you generate the keys and certificates? How do you generate the minimal -data set to start your system. The setup component helps you bootstrap a minimal +data set to start your system? The setup component helps you bootstrap a minimal system. \ No newline at end of file diff --git a/docs/admin/planning/customization.md b/docs/admin/planning/customization.md index 01f15b36bb7..5a7729906b2 100644 --- a/docs/admin/planning/customization.md +++ b/docs/admin/planning/customization.md @@ -36,9 +36,9 @@ which fetches the respective [Facelets](https://en.wikipedia.org/wiki/Facelets) it's possible to mix content such as regular HTML with JSF components. Thus Facelets pages can have both static and **dynamic content** and leverage all your "normal" web design tools like CSS and JavaScript. Facelets also -supports templates. Each `.xhtml` page has access to the authentication context, +support templates. Each `.xhtml` page has access to the authentication context, and you can insert data from the respective interception script. Also, each -`.xhtml` page is unique, and has a built in state identifier, preventing Auth +`.xhtml` page is unique and has a built-in state identifier, preventing Auth Server from responding to any page which it did not render. For more information, see the [Developer Guide](../developer/README.md). @@ -50,7 +50,7 @@ of the subject. You can change the descriptions for the various front-channel Auth Server error messages, for example, what would Auth Server return for a bad -request to the Authorization Endpoint. Of course you can also customize the web +request to the Authorization Endpoint. Of course, you can also customize the web server error messages, like 404, by configuring your web server. Auth Server should **never** return a stackTrace. diff --git a/docs/admin/planning/delegated-user-admin.md b/docs/admin/planning/delegated-user-admin.md index 9e14fe7b4c4..54c9ceadcf5 100644 --- a/docs/admin/planning/delegated-user-admin.md +++ b/docs/admin/planning/delegated-user-admin.md @@ -10,7 +10,7 @@ their organization. You will not be surprised to hear that this is an identity management use case that Janssen Auth Server does not provide out of the box. -But if you wanted to build a web site that performed this function, +But if you wanted to build a website that performed this function, you could use the SCIM protocol to do so. In your application, you could read the user claims to find out the organization, role, or other information about the person managing data. Then your web application diff --git a/docs/admin/planning/dns.md b/docs/admin/planning/dns.md index f890cf605d9..0806d9ea05e 100644 --- a/docs/admin/planning/dns.md +++ b/docs/admin/planning/dns.md @@ -8,7 +8,7 @@ tags: - X.509 --- -Trust on the Internet is largely derived from TLS. Like it or not, we are highly +Trust in the Internet is largely derived from TLS. Like it or not, we are highly reliant on making a secure connection from a web browser using X.509 security to ensure that we are connecting to a trusted web server. The `cn` of that web server certificate is the hostname of the server. There is no guarantee diff --git a/docs/admin/planning/identity-management.md b/docs/admin/planning/identity-management.md index c9e8a26d76a..fc545d86a0a 100644 --- a/docs/admin/planning/identity-management.md +++ b/docs/admin/planning/identity-management.md @@ -20,9 +20,9 @@ workflows to update identity information, and through the use of "connectors", to push this data to all disparate databases. IDM platforms range in size and complexity. An admin could write a Python -script to automate adding new users to a domain. Or large enterprises may +script to automate adding new users to a domain. Large enterprises may implement a commercial IDM platform, like [Sailpoint](https://sailpoint.com) or -an open source IDM platform like [Evolveum Midpoint](https://evolveum.com). +an open-source IDM platform like [Evolveum Midpoint](https://evolveum.com). Or you might have a human IDM--"Hey Bob, we hired a new person. Can you add her?" @@ -47,7 +47,7 @@ the MongoDB database. It's also possible to implement approval workflows using UMA. For example, an API might require an UMA access token (i.e. an RPT token), and obtaining this token may require the consent of two different individuals. -But it is worth remembering that the Janssen Platform was not purpose built for +But it is worth remembering that the Janssen Platform was not purpose-built for IDM, and therefore any implementation for such use cases should be tactical. You may have to build many features yourself. Especially for enterprise workforce applications, you should seriously consider using off-the-shelf diff --git a/docs/admin/planning/kubernetes.md b/docs/admin/planning/kubernetes.md index c8491556e15..da2feca028e 100644 --- a/docs/admin/planning/kubernetes.md +++ b/docs/admin/planning/kubernetes.md @@ -7,60 +7,57 @@ tags: # Overview -This planning guide helps you learn about when to use jans with kubernetes, why to use it, an overview of best practices around it, platforms supported and important tools that can help ease the operations. +This planning guide helps you learn about when to use Jans with Kubernetes, why to use it, an overview of best practices around it, platforms supported and important tools that can help ease the operations. ## The When and Why? -Whether to use kubernetes , vm or a cluster of vms depends on answering several key questions some of which are: +Whether to use Kubernetes , VM or a cluster of VMs depends on answering several key questions some of which are: #### What's the size of my organization/customer serving base? -Answering this question gives an expected load of authentications per second expected which determines if you are in the threshold of operating a VM for jans. Anything past 50 auths per second points to a cluster setup which is curerntly kuberentes. We do plan to support more cloud native setups soon. +Answering this question gives the load of authentications per second expected which determines if you are in the threshold of operating a VM for Jans. Anything past 50 auths per second points to a cluster setup which is curerntly Kuberentes. We do plan to support more cloud-native setups soon. #### Can my organization handle min-hrs of downtime? -This ties to question 1 but even with the best operational automation vm setups restoring/patching a vm will result in downtime. +This ties to question 1 but even with the best operational automation VM setups restoring/patching a VM will result in downtime. #### Does my organization function in different regions? -If your organization works in several regions a vm setup is almost immediately ruled out. +If your organization works in several regions a VM setup is almost immediately ruled out. -#### Does my organization expect to double in growth each year ? or possibly faster? +#### Does my organization expect to double in growth each year? or possibly faster? If your organization or your customer base is growing fast rule out a VM setup. -#### What's the persistence planned to be used in my jans deployment? -If you plan to use LDAP you are almost immediately locked to a VM setup. Our kuberentes deployment supports an LDAP zonal setup only and we generally do not recommend it for a kubernetes setup. +#### What's the persistence planned to be used in my Kans deployment? +If you plan to use LDAP you are almost immediately locked to a VM setup. Our Kuberentes deployment supports an LDAP zonal setup only and we generally do not recommend it for a Kubernetes setup. #### Is this an on-premise vs hybrid vs cloud deployment? -This question weighs on the current infrastructure of your organization. Operating on-premis kubernetes setups needs generally more technical resources than operating a cloud setup. Comparing that to a vm setup, operating a vm setup is much easier in on-premise setups. The more the momentum of your org pulls to cloud vs onpremise the more it pulls to kuberetnes vs a vm setup respectively. +This question weighs on the current infrastructure of your organization. Operating on-premise Kubernetes setups needs generally more technical resources than operating a cloud setup. Comparing that to a VM setup, operating a VM setup is much easier in on-premise setups. The more the momentum of your org pulls to cloud vs onpremise the more it pulls to Kuberetnes vs a VM setup respectively. -#### What's my organizations technical expertise level on kubernetes vs vms? -This determines the amount of investment needed to overcome the learning curve to operate a kubernetes cluster. If your kubernetes technical resources are low and the above questions point to a vm setup you should think about going with a vm setup. If you got conflicting answers above , forexample if the customer size dedicated that you should operate a kubernetes cluster you need to invest in your technical staff. If you are on the borderline invest in your kubernetes technical staff while operating a vm setup and prepare to move in the near future. +#### What's my organizations technical expertise level on Kubernetes vs VMs? +This determines the amount of investment needed to overcome the learning curve to operate a Kubernetes cluster. If your Kubernetes technical resources are low and the above questions point to a VM setup you should think about going with a vm setup. If you got conflicting answers above, for example if the customer size dedicated that you should operate a Kubernetes cluster you need to invest in your technical staff. If you are on the borderline invest in your Kubernetes technical staff while operating a vm setup and prepare to move in the near future. #### Does the deployment need to be highly available(HA)? -We recommend using Kubernetes based CN deployments for situations where high availability is a critical factor. Though +We recommend using Kubernetes-based CN deployments for situations where high availability is a critical factor. Though [VM cluster](./vm-cluster.md) can provide high availability, we do not recommend the HA setup with VMs. Primarily because effort required to upgrade multiple servers and configuring them is much more as compared to a cloud native deployment and it is error-prone. We recommend you follow the CN setup for HA as you will get automatic upgrades, patches with a single helm upgrade command. -In general the kubernetes deployment offers an easy deployment strategy with a helm chart and an easy upgrade path but taking the above into account is very important. +In general the Kubernetes deployment offers an easy deployment strategy with a helm chart and an easy upgrade path but taking the above into account is very important. ## The Supported Clouds -We support several clouds managed kubernetes solutions but that doesn't mean our setup will not work with other managed kubernetes solutions. In fact, our kubernetes setup is expected to work across almost all managed solutions however those not listed below were not tested. -### AWS -Below are example diagrams for popular jans setups with AWS. -### Google -Below are example diagrams for popular jans setups with AWS. -### Azure -Below are example diagrams for popular jans setups with Azure. -### Digital Ocean -Below are example diagrams for popular jans setups with DOKS. +We support several clouds managed Kubernetes solutions but that doesn't mean our setup will not work with other managed Kubernetes solutions. In fact, our Kubernetes setup is expected to work across almost all managed solutions however those not listed below were not tested. + +- AWS +- GCP +- Azure +- DOKS ## Local/Hybrid ### Rancher -Rancher UI can be deployed to several clouds / multi clouds and also be used to manage local setups. +Rancher UI can be deployed to several clouds / multi-clouds and also be used to manage local setups. ## Important tools and tech to consider -- Terraform -- Grafana and Prometheus - Helm -- Pipeline tech such as Jenkins, ansible, cloud build ..etc \ No newline at end of file +- Terraform +- Prometheus and Grafana +- Pipeline tech such as Jenkins, Ansible, Cloud Build ..etc \ No newline at end of file diff --git a/docs/admin/planning/load-balancers.md b/docs/admin/planning/load-balancers.md index c140058f8fc..4004c498923 100644 --- a/docs/admin/planning/load-balancers.md +++ b/docs/admin/planning/load-balancers.md @@ -18,7 +18,7 @@ HTTP Ingress. In your load balancer configuration, you can use any routing algorithm. There is no need for "sticky sessions", or whatever the load balancer you are using calls that. For example, it's ok to use even round robin. Although modern HTTP -ingress controllers enable some very flexibile routing options to do A/B +ingress controllers enable some very flexible routing options to do A/B testing and zero downtime updates. As Janssen Auth Server doesn't really care what load balancer you use, some diff --git a/docs/admin/planning/multi-tenancy.md b/docs/admin/planning/multi-tenancy.md index cfac374066d..4ee6342b84e 100644 --- a/docs/admin/planning/multi-tenancy.md +++ b/docs/admin/planning/multi-tenancy.md @@ -10,11 +10,11 @@ utilize a single software instance. For a federated identity platform, this presents a number of challenges: 1. Privacy: Customers must only see their own user information and data -1. Trust: Customers trust a distinct set of RP's -1. Authorization: Customers have specific police requirements +1. Trust: Customers trust a distinct set of RPs +1. Authorization: Customers have specific policy requirements 1. UX: Customers brand all user-facing web pages and messages 1. Logs: Customers see only their own log -1. Custom Business Logic: Customers have special rules, for example to +1. Custom Business Logic: Customers have special rules, for example, to authenticate users, register clients, or issue access tokens. 1. Cryptographic Keys: Customers have their own keys 1. URLs: Customers host the IDP using their own domain name @@ -28,15 +28,15 @@ easier to operate, saves money on hardware, but requires a lot more code. Or you could land somewhere between--share some systems, but not others. If you want to address all the challenges of multitenancy, then a "shared -nothing" approach makes the most sense. And with advances in cloud native +nothing" approach makes the most sense. And with advances in cloud-native deployment, gitops, and configuration as code, you can approach the cost savings of "shared everything" multitenancy today, especially if you leverage serverless, -just in time auto-scaling. However, you will need some cloud natiuve devops +just in time auto-scaling. However, you will need some cloud-native devops gurus to pull this off. -If having one top level domain is acceptable, it is possible to add a `tenant_id` +If having one top-level domain is acceptable, it is possible to add a `tenant_id` property to each entity (for example, client and person entities). Auth Server -and SCIM interceptions scripts enable you to filter results by adding this +and SCIM interception scripts enable you to filter results by adding this `tenant_id` to queries behind the scenes. For example, you could also render different login pages by using `default_acr_values` for clients. diff --git a/docs/admin/planning/passwordless-auth.md b/docs/admin/planning/passwordless-auth.md index f8973346d1d..758c4a156a8 100644 --- a/docs/admin/planning/passwordless-auth.md +++ b/docs/admin/planning/passwordless-auth.md @@ -2,6 +2,7 @@ tags: - administration - planning + - passwordless --- Auth Server is not proscriptive about how an organization authenticates a @@ -23,7 +24,7 @@ web pages to establish that identity. These pages can ask for any "factors". For example, if you want to perform two factor authentication in one step, you could use a FIDO 2 credential, which combines possession with either knowledge or biometric. But in practice, you could ask for any one or more -combination of credentials--none of which must include password. +combinations of credentials--none of which must include a password. Net-net, "passwordless" is really just marketing jargon. Normally it implies some kind of risk assessment to optimize user experience. If you can imagine diff --git a/docs/admin/planning/persistence.md b/docs/admin/planning/persistence.md index 19f7d915012..0237d33f4d2 100644 --- a/docs/admin/planning/persistence.md +++ b/docs/admin/planning/persistence.md @@ -31,7 +31,7 @@ the pros and cons of the various databases we currently support. 1. **OpenDJ (LDAP)** Janssen supports Gluu's distribution of OpenDJ, and probably any other similar distributions like ForgeRock OpenDJ, Ping Directory Server, or Oracle Unified Directory. LDAP in general and OpenDJ in particular have been -successfully backing authentication service for more then 20 years. People tend +successfully backing authentication service for more than 20 years. People tend to think of the LDAP tree structure as fast for reads, and slow for writes. That's just not true anymore--OpenDJ is able to perform quite well for write operations as well. OpenDJ has mature replication support, excellent command @@ -40,8 +40,8 @@ of OpenDJ is scaling large datasets for high concurrency. While you can get around this shortcoming with a global LDAP proxy, such a topology gets complicated and costly to operate, as you have to break up the data and configure multiple replicated topologies. As a rule of thumb, if concurrency of -more then 120 OpenID code flow authentications per second are needed, you should -consider another database. But for concurrency less then this, OpenDJ is an +more than 120 OpenID code flow authentications per second are needed, you should +consider another database. But for concurrency less than this, OpenDJ is an excellent choice. Owing to these limitations, **LDAP is not supported in production deployments using Kubernetes, 1.0.23 and forward**. @@ -55,19 +55,19 @@ distributions of Postgres like [EnterpriseDB](https://www.enterprisedb.com/). ** persistence for VM based non-production deployments**. 1. **Couchbase** A JSON NoSQL database that supports automatic distribution -of data for auto-scaling multi-region sharded cloud native deployments. Janssen +of data for auto-scaling multi-region sharded cloud-native deployments. Janssen only supports the commercial distribution--but the previously mentioned database properties are enterprise class. If you need to host your own database, and you -need infinite horizontal scalability, Couchbase should be your goto choice. +need infinite horizontal scalability, Couchbase should be your go-to choice. 1. **Aurora** So you want MySQL, but you want Amazon to handle some of the care and feeding? Aurora enables you to consume database as a cloud service. Scalability is excellent and multi-region deployments are [possible](https://aws.amazon.com/blogs/database/deploy-multi-region-amazon-aurora-applications-with-a-failover-blueprint/). The main catch is that write operations are limited to one region, with the -ability failover to another region. But to accomplish this, you need a cloud +ability to failover to another region. But to accomplish this, you need a cloud engineer to implement it. 1. **Spanner** Google's multi-region cloud database as a service, Spanner -was purpose built for auto-scaling, multi-region persistence. It has it's own +was purpose-built for auto-scaling, and multi-region persistence. It has its own API, although recently Google added support for MySQL and Postgres drivers. diff --git a/docs/admin/planning/platform-goal.md b/docs/admin/planning/platform-goal.md index aeaf0802e8f..8ed71fb4801 100644 --- a/docs/admin/planning/platform-goal.md +++ b/docs/admin/planning/platform-goal.md @@ -15,10 +15,10 @@ standards-based identity services. Using Janssen Project software, organizations can build *runtime* identity services to meet 100% of their requirements for enrollment, authentication, credential management, and authorization. The Janssen Project includes software -tools and services for deploying, operating, testing and developing identity +tools and services for deploying, operating, testing, and developing identity infrastructure at scale. -Scale is more than cloud native design patterns. To truly scale, domains +Scale is more than cloud-native design patterns. To truly scale, domains have to consider the people and organizational challenges. To scale domains need to: @@ -44,7 +44,7 @@ with regard to scaling identity infrastructure. Janssen Project tackles the most challenging security requirements. This means keeping current with OpenID and FIDO self-certifications, creating distributions -that enabling conformance with FIPS 140-2, and implementing best practices for +that enables conformance with FIPS 140-2, and implementing best practices for software development. Janssen Project is unapologetically Java. The reason is simple: Java has the @@ -63,15 +63,15 @@ community. Developers don't want to contribute to a project that might change the license at any moment (e.g. Hashicorp, Elastic, MongoDB). There is room for many companies to productize the Janssen Project software. -Governments can feel safe using Janssen Project--it's been recognized as a +Governments can feel safe using the Janssen Project--it's been recognized as a [Digital Public Good](https://app.digitalpublicgoods.net/a/10470). A healthy -ecosystem for infrastructure software results in long term innovation velocity. +ecosystem for infrastructure software results in long-term innovation velocity. With the introduction of Agama, we're hoping that developers will have an -opportunity to build connectors to third party systems and services. Gluu is +opportunity to build connectors to third-party systems and services. Gluu is hosting the [Agama Lab Explore Catalog](https://agama-lab.gluu.org) to help developers publish their Agama projects, making it easier for the community -to find ready-built projects that encourage re-use of code. +to find ready-built projects that encourage the re-use of code. # Deployment @@ -81,5 +81,5 @@ for non-production instances. * Linux system administrators should have packages for easy installation and update of non-clustered deployments. -* Cloud native engineers should have assets for high-end deployments, +* Cloud-native engineers should have assets for high-end deployments, including high concurrency and high availability. diff --git a/docs/admin/planning/security-best-practices.md b/docs/admin/planning/security-best-practices.md index be9b1b4403c..5c8282e1c5c 100644 --- a/docs/admin/planning/security-best-practices.md +++ b/docs/admin/planning/security-best-practices.md @@ -144,5 +144,5 @@ are defined for the related scopes; though it simplifies initial testing, we recommend disabling this feature in production setups * `umaRestrictResourceToAssociatedClient` won't allow any other client except -the one which registered the resource initially to acquire a RPT for it; it's +the one that registered the resource initially to acquire a RPT for it; it's recommended to have it enabled for production setups diff --git a/docs/admin/planning/self-service-password-2fa.md b/docs/admin/planning/self-service-password-2fa.md index 4a3c560539d..a1ee31b6d70 100644 --- a/docs/admin/planning/self-service-password-2fa.md +++ b/docs/admin/planning/self-service-password-2fa.md @@ -5,6 +5,7 @@ tags: - 2FA - self-service - Account Recovery + - Jans casa --- If your domain offers two-factor authentication, it's a good idea to enable end @@ -15,8 +16,4 @@ credentials on one page. You can build a page like Google on your own website. You need to be able to list, add, and remove 2FA credentials for a given user's account. But another -good option is the Casa web application, which is an [open source project](https://github.com/GluuFederation/casa) from Gluu, licensed under Apache 2.0. Casa supports a number of -authentication mechanism that are already available in Jans Auth Server. See the -[Casa Receipe](https://docs.jans.io/head/admin/recipes/casa/) and the -[Casa Person Authn Script](https://docs.jans.io/head/script-catalog/person_authentication/casa/) -for more information. +good option is the [Jans Casa](https://docs.jans.io/vreplace-janssen-version/casa) web application. \ No newline at end of file diff --git a/docs/admin/planning/timeout-management.md b/docs/admin/planning/timeout-management.md index 93624063a19..cfe3333f8c5 100644 --- a/docs/admin/planning/timeout-management.md +++ b/docs/admin/planning/timeout-management.md @@ -6,7 +6,7 @@ tags: --- Warning: business expectations regarding timeouts may drive you crazy. There -are several timeout values in Janssen Auth Server. And web application and +are several timeout values in Janssen Auth Server. Also, web apps and mobile apps may have their own timeout thresholds. The holy grail of timeouts is when everything times out at the same time--IDP and applications. This is rarely attainable. Normally the application needs to handle gracefully the @@ -16,26 +16,26 @@ first, it may need to trigger a logout event at the OpenID Provider. Below is a list of some of the Auth Server configuration properties for timeouts that you should consider: -1. **sessionIdCookieLifetime**: +1. **sessionIdCookieLifetime** -1. **sessionIdLifetime**: +1. **sessionIdLifetime** -1. **sessionIdUnusedLifetime**: +1. **sessionIdUnusedLifetime** -1. **sessionIdUnauthenticatedUnusedLifetime**: +1. **sessionIdUnauthenticatedUnusedLifetime** -1. **spontaneousScopeLifetime**: +1. **spontaneousScopeLifetime** -1. **refreshTokenLifetime**: +1. **refreshTokenLifetime** -1. **idTokenLifetime**: +1. **idTokenLifetime** -1. **accessTokenLifetime**: +1. **accessTokenLifetime** -1. **cleanServiceInterval**: +1. **cleanServiceInterval** -1. **dynamicRegistrationExpirationTime**: +1. **dynamicRegistrationExpirationTime** -1. **refreshTokenExtendLifetimeOnRotation**: +1. **refreshTokenExtendLifetimeOnRotation** 1. **CIBA, UMA and Device Flow**: have their own specific timeouts. diff --git a/docs/admin/planning/use-cases.md b/docs/admin/planning/use-cases.md index bd056081c9d..e9010d1375d 100644 --- a/docs/admin/planning/use-cases.md +++ b/docs/admin/planning/use-cases.md @@ -70,7 +70,7 @@ with the applications that requested them. Out of the box, Auth Server supports many MFA workflows, including FIDO, passkeys, OATH OTP (HOTP, TOTP), SMS (via Twilio or SMPP), and many more. But you're not limited to the MFA that comes out of the box. Using Person Authentication Scripts, you can implement any -authentication workflow which you can imagine. You can also use the Janssen +authentication workflow that you can imagine. You can also use the Janssen Project's Agama programming language to implement multi-step authentication workflows. @@ -84,10 +84,10 @@ the complexity of cookie sharing between the mobile phone browser SDK, and the mobile browser (assuming you are using the system browser), your results may vary if you actually want SSO. Recently, OpenID has published a new specification draft for [Native SSO for Mobile Apps](https://openid.net/specs/openid-connect-native-sso-1_0.html), -which is on the [roadmap](https://github.com/JanssenProject/jans/issues/2518). +that is on the [roadmap](https://github.com/JanssenProject/jans/issues/2518). There are some other hacky ways you can implement mobile authentication, for example, using the OAuth `password` grant--but this is possible only for first-party -applications, and is generally discouraged, because there is no way to +applications, and is generally discouraged because there is no way to securely store a client secret in the mobile application, which hackers can easily decompile. diff --git a/docs/admin/planning/vm-cluster.md b/docs/admin/planning/vm-cluster.md index eb4edb64cea..fdde6e07044 100644 --- a/docs/admin/planning/vm-cluster.md +++ b/docs/admin/planning/vm-cluster.md @@ -8,40 +8,40 @@ tags: !!! Note For high availability, we [recommend](./kubernetes.md#does-the-deployment-need-to-be-highly-availableha) using - the Cloud Native(CN) deployment instead of VM cluster deployments. + the Cloud-Native(CN) deployment instead of VM cluster deployments. -What if you need four or five nines availability, but cloud native is not -an option? You could cluster Janssen using VM's, but you'll have to do +What if you need four or five nines availability, but cloud-native is not +an option? You could cluster Janssen using VMs, but you'll have to do some legwork, because we don't publish tools for this task. This planning guide will cover some of the things you'll need to consider. -1. **Hostname** Remember when you run the linux setup to use the hostname of the -cluster,not the hostname of the individual server. This is important because -the OpenID Provider metadata needs to use the public hostname (i.e. the URL's +1. **Hostname**: Remember when you run the Linux setup to use the hostname of the +cluster, not the hostname of the individual server. This is important because +the OpenID Provider metadata needs to use the public hostname (i.e. the URLs you'll find at `/.well-known/openid-configuration`) -1. **Load Balancing / SSL** As Auth Server and FIDO (the two Internet facing +1. **Load Balancing / SSL**: As Auth Server and FIDO (the two Internet facing components) are stateless, you can use any load balancer routing algorithm, even round robin. You can also use the load balancer to terminate SSL. -1. **Database** The web services Janssen Components share the database, so +1. **Database**: The web services Janssen Components share the database, so you'll have to use database replication (e.g. OpenDJ replication). You could also use a cloud database that takes care of replication for you. -1. **Cache** You can't use `IN-MEMORY` cache which would have no way to +1. **Cache**: You can't use `IN-MEMORY` cache which would have no way to replicate to the other nodes in the network. You could use the Database for caching, although this will impact performance, although it's only an issue for high concurrency use cases. If you are using Couchbase, it has caching built-in. But if you are another database and need high concurrency, our recommendation is to use Redis for caching, which has less cache hit -misses then Memcached. +misses than Memcached. -1. **Key management** Where to you store the private keys? If on the file +1. **Key management**: Where do you store the private keys? If on the file system, you'll have to make sure that they get securely copied. This is -trickier then it sounds because of key rotation. OpenID Connect working group -suggests key rotation every two day, to make sure developers who write OpenID +trickier than it sounds because of key rotation. OpenID Connect working group +suggests key rotation every two days, to make sure developers who write OpenID applications handle key rotation properly in their code, and don't hardcode the metadata, but retrieve it from the OpenID configuration endpoint. -1. **Customizations** You must copy any libraries, xhtml pages, CSS or +1. **Customizations**: You must copy any libraries, xhtml pages, CSS or javascript must be available on all servers. diff --git a/docs/admin/planning/vm-single-instance.md b/docs/admin/planning/vm-single-instance.md index 23831004418..b3606a829ea 100644 --- a/docs/admin/planning/vm-single-instance.md +++ b/docs/admin/planning/vm-single-instance.md @@ -12,23 +12,23 @@ operation trumps availability. If you do a good job at monitoring, and can restore from backup quickly, it's certainly possible to meet an SLA of 99.9% availability using just one server. -Janssen has linux packages available for SUSE, Red Hat and Ubuntu. One +Janssen has Linux packages available for SUSE, Red Hat and Ubuntu. One operational consideration is that you should `hold` the version of Jans Auth Server, to avoid update during the normal package update process. As many applications may rely on a central IDP, you want to plan updates and have a rollback plan if something goes wrong. An automated, unattended update process for the IDP is too risky. -An important security tradeoffs when you run Janssen on a single VM is that +An important security tradeoff when you run Janssen on a single VM is that services which you want to control access to are running on a server with an Internet-facing ethernet interface: the Config API, database, and SCIM -server. Even though these service are running on `localhost`, if the Internet -facing interface was compromised, network protection could be bypassed. +server. Even though these services are running on `localhost`, if the Internet +facing interface is compromised, network protection could be bypassed. The main advantage of running a single VM is simplicity. Your sys admins won't need any special training. And it will be easy to install, backup, monitor, and configure your deployment. If you have many autonomous domains, -each with their own brand and user identity management process, the simplicity -of running a single IDP might be the best solution. If three nines is acceptable +each with its own brand and user identity management process, the simplicity +of running a single IDP might be the best solution. If three nines are acceptable to your business, the expense of deploying and operating a cluster may not be justified. diff --git a/docs/admin/reference/kubernetes/docker-jans-certmanager.md b/docs/admin/reference/kubernetes/docker-jans-certmanager.md index 5f5200eeba6..e2960f6c500 100644 --- a/docs/admin/reference/kubernetes/docker-jans-certmanager.md +++ b/docs/admin/reference/kubernetes/docker-jans-certmanager.md @@ -201,7 +201,7 @@ spec: spec: containers: - name: auth-key-rotation - image: ghcr.io/janssenproject/jans/certmanager:1.1.4_dev + image: ghcr.io/janssenproject/jans/certmanager:1.1.4-1 resources: requests: memory: "300Mi" diff --git a/docs/admin/reference/kubernetes/docker-jans-configurator.md b/docs/admin/reference/kubernetes/docker-jans-configurator.md index 011e3ac1589..2a1410d4d62 100644 --- a/docs/admin/reference/kubernetes/docker-jans-configurator.md +++ b/docs/admin/reference/kubernetes/docker-jans-configurator.md @@ -147,7 +147,7 @@ To generate initial configmaps and secrets: name: config-generate-params containers: - name: configurator-load - image: ghcr.io/janssenproject/jans/configurator:1.1.4_dev + image: ghcr.io/janssenproject/jans/configurator:1.1.4-1 volumeMounts: - mountPath: /app/db/configuration.json name: config-generate-params @@ -185,7 +185,7 @@ To restore configuration from `configuration.out.json` file: name: config-dump-params containers: - name: configurator-load - image: ghcr.io/janssenproject/jans/configurator:1.1.4_dev + image: ghcr.io/janssenproject/jans/configurator:1.1.4-1 volumeMounts: - mountPath: /app/db/configuration.out.json name: config-dump-params @@ -211,7 +211,7 @@ spec: restartPolicy: Never containers: - name: configurator-dump-job - image: ghcr.io/janssenproject/jans/configurator:1.1.4_dev + image: ghcr.io/janssenproject/jans/configurator:1.1.4-1 command: - /bin/sh - -c diff --git a/docs/admin/reference/kubernetes/helm-chart.md b/docs/admin/reference/kubernetes/helm-chart.md index 62477ef8570..1ef958d5ba0 100644 --- a/docs/admin/reference/kubernetes/helm-chart.md +++ b/docs/admin/reference/kubernetes/helm-chart.md @@ -48,8 +48,8 @@ Kubernetes: `>=v1.22.0-0` | Key | Type | Default | Description | |-----|------|---------|-------------| -| auth-server | object | `{"additionalAnnotations":{},"additionalLabels":{},"customScripts":[],"dnsConfig":{},"dnsPolicy":"","hpa":{"behavior":{},"enabled":true,"maxReplicas":10,"metrics":[],"minReplicas":1,"targetCPUUtilizationPercentage":50},"image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"ghcr.io/janssenproject/jans/auth-server","tag":"1.1.4_dev"},"lifecycle":{},"livenessProbe":{"exec":{"command":["python3","/app/scripts/healthcheck.py"]},"initialDelaySeconds":30,"periodSeconds":30,"timeoutSeconds":5},"pdb":{"enabled":true,"maxUnavailable":"90%"},"readinessProbe":{"exec":{"command":["python3","/app/scripts/healthcheck.py"]},"initialDelaySeconds":25,"periodSeconds":25,"timeoutSeconds":5},"replicas":1,"resources":{"limits":{"cpu":"2500m","memory":"2500Mi"},"requests":{"cpu":"2500m","memory":"2500Mi"}},"topologySpreadConstraints":{},"usrEnvs":{"normal":{},"secret":{}},"volumeMounts":[],"volumes":[]}` | OAuth Authorization Server, the OpenID Connect Provider, the UMA Authorization Server--this is the main Internet facing component of Janssen. It's the service that returns tokens, JWT's and identity assertions. This service must be Internet facing. | -| auth-server-key-rotation | object | `{"additionalAnnotations":{},"additionalLabels":{},"customScripts":[],"dnsConfig":{},"dnsPolicy":"","image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"ghcr.io/janssenproject/jans/certmanager","tag":"1.1.4_dev"},"keysLife":48,"keysPushDelay":0,"keysPushStrategy":"NEWER","keysStrategy":"NEWER","lifecycle":{},"resources":{"limits":{"cpu":"300m","memory":"300Mi"},"requests":{"cpu":"300m","memory":"300Mi"}},"usrEnvs":{"normal":{},"secret":{}},"volumeMounts":[],"volumes":[]}` | Responsible for regenerating auth-keys per x hours | +| auth-server | object | `{"additionalAnnotations":{},"additionalLabels":{},"customScripts":[],"dnsConfig":{},"dnsPolicy":"","hpa":{"behavior":{},"enabled":true,"maxReplicas":10,"metrics":[],"minReplicas":1,"targetCPUUtilizationPercentage":50},"image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"ghcr.io/janssenproject/jans/auth-server","tag":"1.1.4-1"},"lifecycle":{},"livenessProbe":{"exec":{"command":["python3","/app/scripts/healthcheck.py"]},"initialDelaySeconds":30,"periodSeconds":30,"timeoutSeconds":5},"pdb":{"enabled":true,"maxUnavailable":"90%"},"readinessProbe":{"exec":{"command":["python3","/app/scripts/healthcheck.py"]},"initialDelaySeconds":25,"periodSeconds":25,"timeoutSeconds":5},"replicas":1,"resources":{"limits":{"cpu":"2500m","memory":"2500Mi"},"requests":{"cpu":"2500m","memory":"2500Mi"}},"topologySpreadConstraints":{},"usrEnvs":{"normal":{},"secret":{}},"volumeMounts":[],"volumes":[]}` | OAuth Authorization Server, the OpenID Connect Provider, the UMA Authorization Server--this is the main Internet facing component of Janssen. It's the service that returns tokens, JWT's and identity assertions. This service must be Internet facing. | +| auth-server-key-rotation | object | `{"additionalAnnotations":{},"additionalLabels":{},"customScripts":[],"dnsConfig":{},"dnsPolicy":"","image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"ghcr.io/janssenproject/jans/certmanager","tag":"1.1.4-1"},"keysLife":48,"keysPushDelay":0,"keysPushStrategy":"NEWER","keysStrategy":"NEWER","lifecycle":{},"resources":{"limits":{"cpu":"300m","memory":"300Mi"},"requests":{"cpu":"300m","memory":"300Mi"}},"usrEnvs":{"normal":{},"secret":{}},"volumeMounts":[],"volumes":[]}` | Responsible for regenerating auth-keys per x hours | | auth-server-key-rotation.additionalAnnotations | object | `{}` | Additional annotations that will be added across the gateway in the format of {cert-manager.io/issuer: "letsencrypt-prod"} | | auth-server-key-rotation.additionalLabels | object | `{}` | Additional labels that will be added across the gateway in the format of {mylabel: "myapp"} | | auth-server-key-rotation.customScripts | list | `[]` | Add custom scripts that have been mounted to run before the entrypoint. - /tmp/custom.sh - /tmp/custom2.sh | @@ -58,7 +58,7 @@ Kubernetes: `>=v1.22.0-0` | auth-server-key-rotation.image.pullPolicy | string | `"IfNotPresent"` | Image pullPolicy to use for deploying. | | auth-server-key-rotation.image.pullSecrets | list | `[]` | Image Pull Secrets | | auth-server-key-rotation.image.repository | string | `"ghcr.io/janssenproject/jans/certmanager"` | Image to use for deploying. | -| auth-server-key-rotation.image.tag | string | `"1.1.4_dev"` | Image tag to use for deploying. | +| auth-server-key-rotation.image.tag | string | `"1.1.4-1"` | Image tag to use for deploying. | | auth-server-key-rotation.keysLife | int | `48` | Auth server key rotation keys life in hours | | auth-server-key-rotation.keysPushDelay | int | `0` | Delay (in seconds) before pushing private keys to Auth server | | auth-server-key-rotation.keysPushStrategy | string | `"NEWER"` | Set key selection strategy after pushing private keys to Auth server (only takes effect when keysPushDelay value is greater than 0) | @@ -84,7 +84,7 @@ Kubernetes: `>=v1.22.0-0` | auth-server.image.pullPolicy | string | `"IfNotPresent"` | Image pullPolicy to use for deploying. | | auth-server.image.pullSecrets | list | `[]` | Image Pull Secrets | | auth-server.image.repository | string | `"ghcr.io/janssenproject/jans/auth-server"` | Image to use for deploying. | -| auth-server.image.tag | string | `"1.1.4_dev"` | Image tag to use for deploying. | +| auth-server.image.tag | string | `"1.1.4-1"` | Image tag to use for deploying. | | auth-server.livenessProbe | object | `{"exec":{"command":["python3","/app/scripts/healthcheck.py"]},"initialDelaySeconds":30,"periodSeconds":30,"timeoutSeconds":5}` | Configure the liveness healthcheck for the auth server if needed. | | auth-server.livenessProbe.exec | object | `{"command":["python3","/app/scripts/healthcheck.py"]}` | Executes the python3 healthcheck. https://github.com/JanssenProject/docker-jans-auth-server/blob/master/scripts/healthcheck.py | | auth-server.pdb | object | `{"enabled":true,"maxUnavailable":"90%"}` | Configure the PodDisruptionBudget | @@ -101,7 +101,7 @@ Kubernetes: `>=v1.22.0-0` | auth-server.usrEnvs.secret | object | `{}` | Add custom secret envs to the service variable1: value1 | | auth-server.volumeMounts | list | `[]` | Configure any additional volumesMounts that need to be attached to the containers | | auth-server.volumes | list | `[]` | Configure any additional volumes that need to be attached to the pod | -| casa | object | `{"additionalAnnotations":{},"additionalLabels":{},"customScripts":[],"dnsConfig":{},"dnsPolicy":"","hpa":{"behavior":{},"enabled":true,"maxReplicas":10,"metrics":[],"minReplicas":1,"targetCPUUtilizationPercentage":50},"image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"ghcr.io/janssenproject/jans/casa","tag":"1.1.4_dev"},"lifecycle":{},"livenessProbe":{"httpGet":{"path":"/jans-casa/health-check","port":"http-casa"},"initialDelaySeconds":25,"periodSeconds":25,"timeoutSeconds":5},"pdb":{"enabled":true,"maxUnavailable":"90%"},"readinessProbe":{"httpGet":{"path":"/jans-casa/health-check","port":"http-casa"},"initialDelaySeconds":30,"periodSeconds":30,"timeoutSeconds":5},"replicas":1,"resources":{"limits":{"cpu":"500m","memory":"500Mi"},"requests":{"cpu":"500m","memory":"500Mi"}},"topologySpreadConstraints":{},"usrEnvs":{"normal":{},"secret":{}},"volumeMounts":[],"volumes":[]}` | Janssen Casa ("Casa") is a self-service web portal for end-users to manage authentication and authorization preferences for their account in a Janssen Auth Server. | +| casa | object | `{"additionalAnnotations":{},"additionalLabels":{},"customScripts":[],"dnsConfig":{},"dnsPolicy":"","hpa":{"behavior":{},"enabled":true,"maxReplicas":10,"metrics":[],"minReplicas":1,"targetCPUUtilizationPercentage":50},"image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"ghcr.io/janssenproject/jans/casa","tag":"1.1.4-1"},"lifecycle":{},"livenessProbe":{"httpGet":{"path":"/jans-casa/health-check","port":"http-casa"},"initialDelaySeconds":25,"periodSeconds":25,"timeoutSeconds":5},"pdb":{"enabled":true,"maxUnavailable":"90%"},"readinessProbe":{"httpGet":{"path":"/jans-casa/health-check","port":"http-casa"},"initialDelaySeconds":30,"periodSeconds":30,"timeoutSeconds":5},"replicas":1,"resources":{"limits":{"cpu":"500m","memory":"500Mi"},"requests":{"cpu":"500m","memory":"500Mi"}},"topologySpreadConstraints":{},"usrEnvs":{"normal":{},"secret":{}},"volumeMounts":[],"volumes":[]}` | Janssen Casa ("Casa") is a self-service web portal for end-users to manage authentication and authorization preferences for their account in a Janssen Auth Server. | | casa.additionalAnnotations | object | `{}` | Additional annotations that will be added across the gateway in the format of {cert-manager.io/issuer: "letsencrypt-prod"} | | casa.additionalLabels | object | `{}` | Additional labels that will be added across the gateway in the format of {mylabel: "myapp"} | | casa.customScripts | list | `[]` | Add custom scripts that have been mounted to run before the entrypoint. - /tmp/custom.sh - /tmp/custom2.sh | @@ -113,7 +113,7 @@ Kubernetes: `>=v1.22.0-0` | casa.image.pullPolicy | string | `"IfNotPresent"` | Image pullPolicy to use for deploying. | | casa.image.pullSecrets | list | `[]` | Image Pull Secrets | | casa.image.repository | string | `"ghcr.io/janssenproject/jans/casa"` | Image to use for deploying. | -| casa.image.tag | string | `"1.1.4_dev"` | Image tag to use for deploying. | +| casa.image.tag | string | `"1.1.4-1"` | Image tag to use for deploying. | | casa.livenessProbe | object | `{"httpGet":{"path":"/jans-casa/health-check","port":"http-casa"},"initialDelaySeconds":25,"periodSeconds":25,"timeoutSeconds":5}` | Configure the liveness healthcheck for casa if needed. | | casa.livenessProbe.httpGet.path | string | `"/jans-casa/health-check"` | http liveness probe endpoint | | casa.pdb | object | `{"enabled":true,"maxUnavailable":"90%"}` | Configure the PodDisruptionBudget | @@ -131,8 +131,8 @@ Kubernetes: `>=v1.22.0-0` | casa.usrEnvs.secret | object | `{}` | Add custom secret envs to the service variable1: value1 | | casa.volumeMounts | list | `[]` | Configure any additional volumesMounts that need to be attached to the containers | | casa.volumes | list | `[]` | Configure any additional volumes that need to be attached to the pod | -| config | object | `{"additionalAnnotations":{},"additionalLabels":{},"adminPassword":"Test1234#","city":"Austin","configmap":{"cnAwsAccessKeyId":"","cnAwsDefaultRegion":"us-west-1","cnAwsProfile":"janssen","cnAwsSecretAccessKey":"","cnAwsSecretsEndpointUrl":"","cnAwsSecretsNamePrefix":"janssen","cnAwsSecretsReplicaRegions":[],"cnCacheType":"NATIVE_PERSISTENCE","cnConfigKubernetesConfigMap":"cn","cnCouchbaseBucketPrefix":"jans","cnCouchbaseCrt":"SWFtTm90YVNlcnZpY2VBY2NvdW50Q2hhbmdlTWV0b09uZQo=","cnCouchbaseIndexNumReplica":0,"cnCouchbasePassword":"P@ssw0rd","cnCouchbaseSuperUser":"admin","cnCouchbaseSuperUserPassword":"Test1234#","cnCouchbaseUrl":"cbjanssen.default.svc.cluster.local","cnCouchbaseUser":"janssen","cnGoogleProjectId":"google-project-to-save-config-and-secrets-to","cnGoogleSecretManagerServiceAccount":"SWFtTm90YVNlcnZpY2VBY2NvdW50Q2hhbmdlTWV0b09uZQo=","cnGoogleSecretNamePrefix":"janssen","cnGoogleSecretVersionId":"latest","cnGoogleSpannerDatabaseId":"","cnGoogleSpannerInstanceId":"","cnJettyRequestHeaderSize":8192,"cnLdapCrt":"SWFtTm90YVNlcnZpY2VBY2NvdW50Q2hhbmdlTWV0b09uZQo=","cnLdapKey":"SWFtTm90YVNlcnZpY2VBY2NvdW50Q2hhbmdlTWV0b09uZQo=","cnLdapUrl":"opendj:1636","cnMaxRamPercent":"75.0","cnMessageType":"DISABLED","cnOpaUrl":"http://opa.opa.svc.cluster.cluster.local:8181/v1","cnPersistenceHybridMapping":"{}","cnRedisSentinelGroup":"","cnRedisSslTruststore":"","cnRedisType":"STANDALONE","cnRedisUrl":"redis.redis.svc.cluster.local:6379","cnRedisUseSsl":false,"cnScimProtectionMode":"OAUTH","cnSecretKubernetesSecret":"cn","cnSqlDbDialect":"mysql","cnSqlDbHost":"my-release-mysql.default.svc.cluster.local","cnSqlDbName":"jans","cnSqlDbPort":3306,"cnSqlDbSchema":"","cnSqlDbTimezone":"UTC","cnSqlDbUser":"jans","cnSqldbUserPassword":"Test1234#","cnVaultAddr":"http://localhost:8200","cnVaultAppRolePath":"approle","cnVaultKvPath":"secret","cnVaultNamespace":"","cnVaultPrefix":"jans","cnVaultRoleId":"","cnVaultRoleIdFile":"/etc/certs/vault_role_id","cnVaultSecretId":"","cnVaultSecretIdFile":"/etc/certs/vault_secret_id","cnVaultVerify":false,"kcDbPassword":"Test1234#","kcDbSchema":"keycloak","kcDbUrlDatabase":"keycloak","kcDbUrlHost":"mysql.kc.svc.cluster.local","kcDbUrlPort":3306,"kcDbUrlProperties":"?useUnicode=true&characterEncoding=UTF-8&character_set_server=utf8mb4","kcDbUsername":"keycloak","kcDbVendor":"mysql","kcLogLevel":"INFO","lbAddr":"","quarkusTransactionEnableRecovery":true},"countryCode":"US","customScripts":[],"dnsConfig":{},"dnsPolicy":"","email":"support@jans.io","image":{"pullSecrets":[],"repository":"ghcr.io/janssenproject/jans/configurator","tag":"1.1.4_dev"},"ldapPassword":"P@ssw0rds","ldapTruststorePassword":"changeit","lifecycle":{},"orgName":"Janssen","redisPassword":"P@assw0rd","resources":{"limits":{"cpu":"300m","memory":"300Mi"},"requests":{"cpu":"300m","memory":"300Mi"}},"salt":"","state":"TX","usrEnvs":{"normal":{},"secret":{}},"volumeMounts":[],"volumes":[]}` | Configuration parameters for setup and initial configuration secret and config layers used by Janssen services. | -| config-api | object | `{"additionalAnnotations":{},"additionalLabels":{},"customScripts":[],"dnsConfig":{},"dnsPolicy":"","hpa":{"behavior":{},"enabled":true,"maxReplicas":10,"metrics":[],"minReplicas":1,"targetCPUUtilizationPercentage":50},"image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"ghcr.io/janssenproject/jans/config-api","tag":"1.1.4_dev"},"lifecycle":{},"livenessProbe":{"httpGet":{"path":"/jans-config-api/api/v1/health/live","port":8074},"initialDelaySeconds":30,"periodSeconds":30,"timeoutSeconds":5},"pdb":{"enabled":true,"maxUnavailable":"90%"},"readinessProbe":{"httpGet":{"path":"jans-config-api/api/v1/health/ready","port":8074},"initialDelaySeconds":25,"periodSeconds":25,"timeoutSeconds":5},"replicas":1,"resources":{"limits":{"cpu":"1000m","memory":"1200Mi"},"requests":{"cpu":"1000m","memory":"1200Mi"}},"topologySpreadConstraints":{},"usrEnvs":{"normal":{},"secret":{}},"volumeMounts":[],"volumes":[]}` | Config Api endpoints can be used to configure the auth-server, which is an open-source OpenID Connect Provider (OP) and UMA Authorization Server (AS). | +| config | object | `{"additionalAnnotations":{},"additionalLabels":{},"adminPassword":"Test1234#","city":"Austin","configmap":{"cnAwsAccessKeyId":"","cnAwsDefaultRegion":"us-west-1","cnAwsProfile":"janssen","cnAwsSecretAccessKey":"","cnAwsSecretsEndpointUrl":"","cnAwsSecretsNamePrefix":"janssen","cnAwsSecretsReplicaRegions":[],"cnCacheType":"NATIVE_PERSISTENCE","cnConfigKubernetesConfigMap":"cn","cnCouchbaseBucketPrefix":"jans","cnCouchbaseCrt":"SWFtTm90YVNlcnZpY2VBY2NvdW50Q2hhbmdlTWV0b09uZQo=","cnCouchbaseIndexNumReplica":0,"cnCouchbasePassword":"P@ssw0rd","cnCouchbaseSuperUser":"admin","cnCouchbaseSuperUserPassword":"Test1234#","cnCouchbaseUrl":"cbjanssen.default.svc.cluster.local","cnCouchbaseUser":"janssen","cnGoogleProjectId":"google-project-to-save-config-and-secrets-to","cnGoogleSecretManagerServiceAccount":"SWFtTm90YVNlcnZpY2VBY2NvdW50Q2hhbmdlTWV0b09uZQo=","cnGoogleSecretNamePrefix":"janssen","cnGoogleSecretVersionId":"latest","cnGoogleSpannerDatabaseId":"","cnGoogleSpannerInstanceId":"","cnJettyRequestHeaderSize":8192,"cnLdapCrt":"SWFtTm90YVNlcnZpY2VBY2NvdW50Q2hhbmdlTWV0b09uZQo=","cnLdapKey":"SWFtTm90YVNlcnZpY2VBY2NvdW50Q2hhbmdlTWV0b09uZQo=","cnLdapUrl":"opendj:1636","cnMaxRamPercent":"75.0","cnMessageType":"DISABLED","cnOpaUrl":"http://opa.opa.svc.cluster.cluster.local:8181/v1","cnPersistenceHybridMapping":"{}","cnRedisSentinelGroup":"","cnRedisSslTruststore":"","cnRedisType":"STANDALONE","cnRedisUrl":"redis.redis.svc.cluster.local:6379","cnRedisUseSsl":false,"cnScimProtectionMode":"OAUTH","cnSecretKubernetesSecret":"cn","cnSqlDbDialect":"mysql","cnSqlDbHost":"my-release-mysql.default.svc.cluster.local","cnSqlDbName":"jans","cnSqlDbPort":3306,"cnSqlDbSchema":"","cnSqlDbTimezone":"UTC","cnSqlDbUser":"jans","cnSqldbUserPassword":"Test1234#","cnVaultAddr":"http://localhost:8200","cnVaultAppRolePath":"approle","cnVaultKvPath":"secret","cnVaultNamespace":"","cnVaultPrefix":"jans","cnVaultRoleId":"","cnVaultRoleIdFile":"/etc/certs/vault_role_id","cnVaultSecretId":"","cnVaultSecretIdFile":"/etc/certs/vault_secret_id","cnVaultVerify":false,"kcDbPassword":"Test1234#","kcDbSchema":"keycloak","kcDbUrlDatabase":"keycloak","kcDbUrlHost":"mysql.kc.svc.cluster.local","kcDbUrlPort":3306,"kcDbUrlProperties":"?useUnicode=true&characterEncoding=UTF-8&character_set_server=utf8mb4","kcDbUsername":"keycloak","kcDbVendor":"mysql","kcLogLevel":"INFO","lbAddr":"","quarkusTransactionEnableRecovery":true},"countryCode":"US","customScripts":[],"dnsConfig":{},"dnsPolicy":"","email":"support@jans.io","image":{"pullSecrets":[],"repository":"ghcr.io/janssenproject/jans/configurator","tag":"1.1.4-1"},"ldapPassword":"P@ssw0rds","ldapTruststorePassword":"changeit","lifecycle":{},"orgName":"Janssen","redisPassword":"P@assw0rd","resources":{"limits":{"cpu":"300m","memory":"300Mi"},"requests":{"cpu":"300m","memory":"300Mi"}},"salt":"","state":"TX","usrEnvs":{"normal":{},"secret":{}},"volumeMounts":[],"volumes":[]}` | Configuration parameters for setup and initial configuration secret and config layers used by Janssen services. | +| config-api | object | `{"additionalAnnotations":{},"additionalLabels":{},"customScripts":[],"dnsConfig":{},"dnsPolicy":"","hpa":{"behavior":{},"enabled":true,"maxReplicas":10,"metrics":[],"minReplicas":1,"targetCPUUtilizationPercentage":50},"image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"ghcr.io/janssenproject/jans/config-api","tag":"1.1.4-1"},"lifecycle":{},"livenessProbe":{"httpGet":{"path":"/jans-config-api/api/v1/health/live","port":8074},"initialDelaySeconds":30,"periodSeconds":30,"timeoutSeconds":5},"pdb":{"enabled":true,"maxUnavailable":"90%"},"readinessProbe":{"httpGet":{"path":"jans-config-api/api/v1/health/ready","port":8074},"initialDelaySeconds":25,"periodSeconds":25,"timeoutSeconds":5},"replicas":1,"resources":{"limits":{"cpu":"1000m","memory":"1200Mi"},"requests":{"cpu":"1000m","memory":"1200Mi"}},"topologySpreadConstraints":{},"usrEnvs":{"normal":{},"secret":{}},"volumeMounts":[],"volumes":[]}` | Config Api endpoints can be used to configure the auth-server, which is an open-source OpenID Connect Provider (OP) and UMA Authorization Server (AS). | | config-api.additionalAnnotations | object | `{}` | Additional annotations that will be added across the gateway in the format of {cert-manager.io/issuer: "letsencrypt-prod"} | | config-api.additionalLabels | object | `{}` | Additional labels that will be added across the gateway in the format of {mylabel: "myapp"} | | config-api.customScripts | list | `[]` | Add custom scripts that have been mounted to run before the entrypoint. - /tmp/custom.sh - /tmp/custom2.sh | @@ -144,7 +144,7 @@ Kubernetes: `>=v1.22.0-0` | config-api.image.pullPolicy | string | `"IfNotPresent"` | Image pullPolicy to use for deploying. | | config-api.image.pullSecrets | list | `[]` | Image Pull Secrets | | config-api.image.repository | string | `"ghcr.io/janssenproject/jans/config-api"` | Image to use for deploying. | -| config-api.image.tag | string | `"1.1.4_dev"` | Image tag to use for deploying. | +| config-api.image.tag | string | `"1.1.4-1"` | Image tag to use for deploying. | | config-api.livenessProbe | object | `{"httpGet":{"path":"/jans-config-api/api/v1/health/live","port":8074},"initialDelaySeconds":30,"periodSeconds":30,"timeoutSeconds":5}` | Configure the liveness healthcheck for the auth server if needed. | | config-api.livenessProbe.httpGet | object | `{"path":"/jans-config-api/api/v1/health/live","port":8074}` | http liveness probe endpoint | | config-api.pdb | object | `{"enabled":true,"maxUnavailable":"90%"}` | Configure the PodDisruptionBudget | @@ -231,7 +231,7 @@ Kubernetes: `>=v1.22.0-0` | config.email | string | `"support@jans.io"` | Email address of the administrator usually. Used for certificate creation. | | config.image.pullSecrets | list | `[]` | Image Pull Secrets | | config.image.repository | string | `"ghcr.io/janssenproject/jans/configurator"` | Image to use for deploying. | -| config.image.tag | string | `"1.1.4_dev"` | Image tag to use for deploying. | +| config.image.tag | string | `"1.1.4-1"` | Image tag to use for deploying. | | config.ldapPassword | string | `"P@ssw0rds"` | LDAP admin password if OpenDJ is used for persistence. | | config.ldapTruststorePassword | string | `"changeit"` | LDAP truststore password if OpenDJ is used for persistence | | config.orgName | string | `"Janssen"` | Organization name. Used for certificate creation. | @@ -248,7 +248,7 @@ Kubernetes: `>=v1.22.0-0` | config.usrEnvs.secret | object | `{}` | Add custom secret envs to the service. variable1: value1 | | config.volumeMounts | list | `[]` | Configure any additional volumesMounts that need to be attached to the containers | | config.volumes | list | `[]` | Configure any additional volumes that need to be attached to the pod | -| fido2 | object | `{"additionalAnnotations":{},"additionalLabels":{},"customScripts":[],"dnsConfig":{},"dnsPolicy":"","hpa":{"behavior":{},"enabled":true,"maxReplicas":10,"metrics":[],"minReplicas":1,"targetCPUUtilizationPercentage":50},"image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"ghcr.io/janssenproject/jans/fido2","tag":"1.1.4_dev"},"lifecycle":{},"livenessProbe":{"httpGet":{"path":"/jans-fido2/sys/health-check","port":"http-fido2"},"initialDelaySeconds":25,"periodSeconds":25,"timeoutSeconds":5},"pdb":{"enabled":true,"maxUnavailable":"90%"},"readinessProbe":{"httpGet":{"path":"/jans-fido2/sys/health-check","port":"http-fido2"},"initialDelaySeconds":30,"periodSeconds":30,"timeoutSeconds":5},"replicas":1,"resources":{"limits":{"cpu":"500m","memory":"500Mi"},"requests":{"cpu":"500m","memory":"500Mi"}},"service":{"name":"http-fido2","port":8080},"topologySpreadConstraints":{},"usrEnvs":{"normal":{},"secret":{}},"volumeMounts":[],"volumes":[]}` | FIDO 2.0 (FIDO2) is an open authentication standard that enables leveraging common devices to authenticate to online services in both mobile and desktop environments. | +| fido2 | object | `{"additionalAnnotations":{},"additionalLabels":{},"customScripts":[],"dnsConfig":{},"dnsPolicy":"","hpa":{"behavior":{},"enabled":true,"maxReplicas":10,"metrics":[],"minReplicas":1,"targetCPUUtilizationPercentage":50},"image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"ghcr.io/janssenproject/jans/fido2","tag":"1.1.4-1"},"lifecycle":{},"livenessProbe":{"httpGet":{"path":"/jans-fido2/sys/health-check","port":"http-fido2"},"initialDelaySeconds":25,"periodSeconds":25,"timeoutSeconds":5},"pdb":{"enabled":true,"maxUnavailable":"90%"},"readinessProbe":{"httpGet":{"path":"/jans-fido2/sys/health-check","port":"http-fido2"},"initialDelaySeconds":30,"periodSeconds":30,"timeoutSeconds":5},"replicas":1,"resources":{"limits":{"cpu":"500m","memory":"500Mi"},"requests":{"cpu":"500m","memory":"500Mi"}},"service":{"name":"http-fido2","port":8080},"topologySpreadConstraints":{},"usrEnvs":{"normal":{},"secret":{}},"volumeMounts":[],"volumes":[]}` | FIDO 2.0 (FIDO2) is an open authentication standard that enables leveraging common devices to authenticate to online services in both mobile and desktop environments. | | fido2.additionalAnnotations | object | `{}` | Additional annotations that will be added across the gateway in the format of {cert-manager.io/issuer: "letsencrypt-prod"} | | fido2.additionalLabels | object | `{}` | Additional labels that will be added across the gateway in the format of {mylabel: "myapp"} | | fido2.customScripts | list | `[]` | Add custom scripts that have been mounted to run before the entrypoint. - /tmp/custom.sh - /tmp/custom2.sh | @@ -260,7 +260,7 @@ Kubernetes: `>=v1.22.0-0` | fido2.image.pullPolicy | string | `"IfNotPresent"` | Image pullPolicy to use for deploying. | | fido2.image.pullSecrets | list | `[]` | Image Pull Secrets | | fido2.image.repository | string | `"ghcr.io/janssenproject/jans/fido2"` | Image to use for deploying. | -| fido2.image.tag | string | `"1.1.4_dev"` | Image tag to use for deploying. | +| fido2.image.tag | string | `"1.1.4-1"` | Image tag to use for deploying. | | fido2.livenessProbe | object | `{"httpGet":{"path":"/jans-fido2/sys/health-check","port":"http-fido2"},"initialDelaySeconds":25,"periodSeconds":25,"timeoutSeconds":5}` | Configure the liveness healthcheck for the fido2 if needed. | | fido2.livenessProbe.httpGet | object | `{"path":"/jans-fido2/sys/health-check","port":"http-fido2"}` | http liveness probe endpoint | | fido2.pdb | object | `{"enabled":true,"maxUnavailable":"90%"}` | Configure the PodDisruptionBudget | @@ -440,7 +440,7 @@ Kubernetes: `>=v1.22.0-0` | global.usrEnvs | object | `{"normal":{},"secret":{}}` | Add custom normal and secret envs to the service. Envs defined in global.userEnvs will be globally available to all services | | global.usrEnvs.normal | object | `{}` | Add custom normal envs to the service. variable1: value1 | | global.usrEnvs.secret | object | `{}` | Add custom secret envs to the service. variable1: value1 | -| kc-scheduler | object | `{"additionalAnnotations":{},"additionalLabels":{},"customScripts":[],"dnsConfig":{},"dnsPolicy":"","image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"ghcr.io/janssenproject/jans/kc-scheduler","tag":"1.1.4_dev"},"interval":10,"lifecycle":{},"resources":{"limits":{"cpu":"300m","memory":"300Mi"},"requests":{"cpu":"300m","memory":"300Mi"}},"usrEnvs":{"normal":{},"secret":{}},"volumeMounts":[],"volumes":[]}` | Responsible for synchronizing Keycloak SAML clients | +| kc-scheduler | object | `{"additionalAnnotations":{},"additionalLabels":{},"customScripts":[],"dnsConfig":{},"dnsPolicy":"","image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"ghcr.io/janssenproject/jans/kc-scheduler","tag":"1.1.4-1"},"interval":10,"lifecycle":{},"resources":{"limits":{"cpu":"300m","memory":"300Mi"},"requests":{"cpu":"300m","memory":"300Mi"}},"usrEnvs":{"normal":{},"secret":{}},"volumeMounts":[],"volumes":[]}` | Responsible for synchronizing Keycloak SAML clients | | kc-scheduler.additionalAnnotations | object | `{}` | Additional annotations that will be added across the gateway in the format of {cert-manager.io/issuer: "letsencrypt-prod"} | | kc-scheduler.additionalLabels | object | `{}` | Additional labels that will be added across the gateway in the format of {mylabel: "myapp"} | | kc-scheduler.customScripts | list | `[]` | Add custom scripts that have been mounted to run before the entrypoint. - /tmp/custom.sh - /tmp/custom2.sh | @@ -449,7 +449,7 @@ Kubernetes: `>=v1.22.0-0` | kc-scheduler.image.pullPolicy | string | `"IfNotPresent"` | Image pullPolicy to use for deploying. | | kc-scheduler.image.pullSecrets | list | `[]` | Image Pull Secrets | | kc-scheduler.image.repository | string | `"ghcr.io/janssenproject/jans/kc-scheduler"` | Image to use for deploying. | -| kc-scheduler.image.tag | string | `"1.1.4_dev"` | Image tag to use for deploying. | +| kc-scheduler.image.tag | string | `"1.1.4-1"` | Image tag to use for deploying. | | kc-scheduler.interval | int | `10` | Interval of running the scheduler (in minutes) | | kc-scheduler.resources | object | `{"limits":{"cpu":"300m","memory":"300Mi"},"requests":{"cpu":"300m","memory":"300Mi"}}` | Resource specs. | | kc-scheduler.resources.limits.cpu | string | `"300m"` | CPU limit. | @@ -461,7 +461,7 @@ Kubernetes: `>=v1.22.0-0` | kc-scheduler.usrEnvs.secret | object | `{}` | Add custom secret envs to the service variable1: value1 | | kc-scheduler.volumeMounts | list | `[]` | Configure any additional volumesMounts that need to be attached to the containers | | kc-scheduler.volumes | list | `[]` | Configure any additional volumes that need to be attached to the pod | -| link | object | `{"additionalAnnotations":{},"additionalLabels":{},"customScripts":[],"dnsConfig":{},"dnsPolicy":"","hpa":{"behavior":{},"enabled":true,"maxReplicas":10,"metrics":[],"minReplicas":1,"targetCPUUtilizationPercentage":50},"image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"ghcr.io/janssenproject/jans/link","tag":"1.1.4_dev"},"lifecycle":{},"livenessProbe":{"exec":{"command":["python3","/app/scripts/healthcheck.py"]},"initialDelaySeconds":30,"periodSeconds":30,"timeoutSeconds":5},"pdb":{"enabled":true,"maxUnavailable":"90%"},"readinessProbe":{"exec":{"command":["python3","/app/scripts/healthcheck.py"]},"initialDelaySeconds":25,"periodSeconds":25,"timeoutSeconds":5},"replicas":1,"resources":{"limits":{"cpu":"500m","memory":"1200Mi"},"requests":{"cpu":"500m","memory":"1200Mi"}},"topologySpreadConstraints":{},"usrEnvs":{"normal":{},"secret":{}},"volumeMounts":[],"volumes":[]}` | Link. | +| link | object | `{"additionalAnnotations":{},"additionalLabels":{},"customScripts":[],"dnsConfig":{},"dnsPolicy":"","hpa":{"behavior":{},"enabled":true,"maxReplicas":10,"metrics":[],"minReplicas":1,"targetCPUUtilizationPercentage":50},"image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"ghcr.io/janssenproject/jans/link","tag":"1.1.4-1"},"lifecycle":{},"livenessProbe":{"exec":{"command":["python3","/app/scripts/healthcheck.py"]},"initialDelaySeconds":30,"periodSeconds":30,"timeoutSeconds":5},"pdb":{"enabled":true,"maxUnavailable":"90%"},"readinessProbe":{"exec":{"command":["python3","/app/scripts/healthcheck.py"]},"initialDelaySeconds":25,"periodSeconds":25,"timeoutSeconds":5},"replicas":1,"resources":{"limits":{"cpu":"500m","memory":"1200Mi"},"requests":{"cpu":"500m","memory":"1200Mi"}},"topologySpreadConstraints":{},"usrEnvs":{"normal":{},"secret":{}},"volumeMounts":[],"volumes":[]}` | Link. | | link.additionalAnnotations | object | `{}` | Additional annotations that will be added across the gateway in the format of {cert-manager.io/issuer: "letsencrypt-prod"} | | link.additionalLabels | object | `{}` | Additional labels that will be added across the gateway in the format of {mylabel: "myapp"} | | link.customScripts | list | `[]` | Add custom scripts that have been mounted to run before the entrypoint. - /tmp/custom.sh - /tmp/custom2.sh | @@ -473,7 +473,7 @@ Kubernetes: `>=v1.22.0-0` | link.image.pullPolicy | string | `"IfNotPresent"` | Image pullPolicy to use for deploying. | | link.image.pullSecrets | list | `[]` | Image Pull Secrets | | link.image.repository | string | `"ghcr.io/janssenproject/jans/link"` | Image to use for deploying. | -| link.image.tag | string | `"1.1.4_dev"` | Image tag to use for deploying. | +| link.image.tag | string | `"1.1.4-1"` | Image tag to use for deploying. | | link.livenessProbe | object | `{"exec":{"command":["python3","/app/scripts/healthcheck.py"]},"initialDelaySeconds":30,"periodSeconds":30,"timeoutSeconds":5}` | Configure the liveness healthcheck for the auth server if needed. | | link.livenessProbe.exec | object | `{"command":["python3","/app/scripts/healthcheck.py"]}` | http liveness probe endpoint | | link.pdb | object | `{"enabled":true,"maxUnavailable":"90%"}` | Configure the PodDisruptionBudget | @@ -557,7 +557,7 @@ Kubernetes: `>=v1.22.0-0` | opendj.usrEnvs.secret | object | `{}` | Add custom secret envs to the service variable1: value1 | | opendj.volumeMounts | list | `[]` | Configure any additional volumesMounts that need to be attached to the containers | | opendj.volumes | list | `[]` | Configure any additional volumes that need to be attached to the pod | -| persistence | object | `{"additionalAnnotations":{},"additionalLabels":{},"customScripts":[],"dnsConfig":{},"dnsPolicy":"","image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"ghcr.io/janssenproject/jans/persistence-loader","tag":"1.1.4_dev"},"lifecycle":{},"resources":{"limits":{"cpu":"300m","memory":"300Mi"},"requests":{"cpu":"300m","memory":"300Mi"}},"usrEnvs":{"normal":{},"secret":{}},"volumeMounts":[],"volumes":[]}` | Job to generate data and initial config for Janssen Server persistence layer. | +| persistence | object | `{"additionalAnnotations":{},"additionalLabels":{},"customScripts":[],"dnsConfig":{},"dnsPolicy":"","image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"ghcr.io/janssenproject/jans/persistence-loader","tag":"1.1.4-1"},"lifecycle":{},"resources":{"limits":{"cpu":"300m","memory":"300Mi"},"requests":{"cpu":"300m","memory":"300Mi"}},"usrEnvs":{"normal":{},"secret":{}},"volumeMounts":[],"volumes":[]}` | Job to generate data and initial config for Janssen Server persistence layer. | | persistence.additionalAnnotations | object | `{}` | Additional annotations that will be added across the gateway in the format of {cert-manager.io/issuer: "letsencrypt-prod"} | | persistence.additionalLabels | object | `{}` | Additional labels that will be added across the gateway in the format of {mylabel: "myapp"} | | persistence.customScripts | list | `[]` | Add custom scripts that have been mounted to run before the entrypoint. - /tmp/custom.sh - /tmp/custom2.sh | @@ -566,7 +566,7 @@ Kubernetes: `>=v1.22.0-0` | persistence.image.pullPolicy | string | `"IfNotPresent"` | Image pullPolicy to use for deploying. | | persistence.image.pullSecrets | list | `[]` | Image Pull Secrets | | persistence.image.repository | string | `"ghcr.io/janssenproject/jans/persistence-loader"` | Image to use for deploying. | -| persistence.image.tag | string | `"1.1.4_dev"` | Image tag to use for deploying. | +| persistence.image.tag | string | `"1.1.4-1"` | Image tag to use for deploying. | | persistence.resources | object | `{"limits":{"cpu":"300m","memory":"300Mi"},"requests":{"cpu":"300m","memory":"300Mi"}}` | Resource specs. | | persistence.resources.limits.cpu | string | `"300m"` | CPU limit | | persistence.resources.limits.memory | string | `"300Mi"` | Memory limit. | @@ -577,7 +577,7 @@ Kubernetes: `>=v1.22.0-0` | persistence.usrEnvs.secret | object | `{}` | Add custom secret envs to the service variable1: value1 | | persistence.volumeMounts | list | `[]` | Configure any additional volumesMounts that need to be attached to the containers | | persistence.volumes | list | `[]` | Configure any additional volumes that need to be attached to the pod | -| saml | object | `{"additionalAnnotations":{},"additionalLabels":{},"customScripts":[],"dnsConfig":{},"dnsPolicy":"","hpa":{"behavior":{},"enabled":true,"maxReplicas":10,"metrics":[],"minReplicas":1,"targetCPUUtilizationPercentage":50},"image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"ghcr.io/janssenproject/jans/saml","tag":"1.1.4_dev"},"lifecycle":{},"livenessProbe":{"exec":{"command":["python3","/app/scripts/healthcheck.py"]},"failureThreshold":10,"initialDelaySeconds":30,"periodSeconds":30,"timeoutSeconds":5},"pdb":{"enabled":true,"maxUnavailable":"90%"},"readinessProbe":{"exec":{"command":["python3","/app/scripts/healthcheck.py"]},"failureThreshold":10,"initialDelaySeconds":25,"periodSeconds":25,"timeoutSeconds":5},"replicas":1,"resources":{"limits":{"cpu":"500m","memory":"1200Mi"},"requests":{"cpu":"500m","memory":"1200Mi"}},"topologySpreadConstraints":{},"usrEnvs":{"normal":{},"secret":{}},"volumeMounts":[],"volumes":[]}` | SAML. | +| saml | object | `{"additionalAnnotations":{},"additionalLabels":{},"customScripts":[],"dnsConfig":{},"dnsPolicy":"","hpa":{"behavior":{},"enabled":true,"maxReplicas":10,"metrics":[],"minReplicas":1,"targetCPUUtilizationPercentage":50},"image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"ghcr.io/janssenproject/jans/saml","tag":"1.1.4-1"},"lifecycle":{},"livenessProbe":{"exec":{"command":["python3","/app/scripts/healthcheck.py"]},"failureThreshold":10,"initialDelaySeconds":30,"periodSeconds":30,"timeoutSeconds":5},"pdb":{"enabled":true,"maxUnavailable":"90%"},"readinessProbe":{"exec":{"command":["python3","/app/scripts/healthcheck.py"]},"failureThreshold":10,"initialDelaySeconds":25,"periodSeconds":25,"timeoutSeconds":5},"replicas":1,"resources":{"limits":{"cpu":"500m","memory":"1200Mi"},"requests":{"cpu":"500m","memory":"1200Mi"}},"topologySpreadConstraints":{},"usrEnvs":{"normal":{},"secret":{}},"volumeMounts":[],"volumes":[]}` | SAML. | | saml.additionalAnnotations | object | `{}` | Additional annotations that will be added across the gateway in the format of {cert-manager.io/issuer: "letsencrypt-prod"} | | saml.additionalLabels | object | `{}` | Additional labels that will be added across the gateway in the format of {mylabel: "myapp"} | | saml.customScripts | list | `[]` | Add custom scripts that have been mounted to run before the entrypoint. - /tmp/custom.sh - /tmp/custom2.sh | @@ -589,7 +589,7 @@ Kubernetes: `>=v1.22.0-0` | saml.image.pullPolicy | string | `"IfNotPresent"` | Image pullPolicy to use for deploying. | | saml.image.pullSecrets | list | `[]` | Image Pull Secrets | | saml.image.repository | string | `"ghcr.io/janssenproject/jans/saml"` | Image to use for deploying. | -| saml.image.tag | string | `"1.1.4_dev"` | Image tag to use for deploying. | +| saml.image.tag | string | `"1.1.4-1"` | Image tag to use for deploying. | | saml.livenessProbe | object | `{"exec":{"command":["python3","/app/scripts/healthcheck.py"]},"failureThreshold":10,"initialDelaySeconds":30,"periodSeconds":30,"timeoutSeconds":5}` | Configure the liveness healthcheck for the auth server if needed. | | saml.livenessProbe.exec | object | `{"command":["python3","/app/scripts/healthcheck.py"]}` | http liveness probe endpoint | | saml.pdb | object | `{"enabled":true,"maxUnavailable":"90%"}` | Configure the PodDisruptionBudget | @@ -606,7 +606,7 @@ Kubernetes: `>=v1.22.0-0` | saml.usrEnvs.secret | object | `{}` | Add custom secret envs to the service variable1: value1 | | saml.volumeMounts | list | `[]` | Configure any additional volumesMounts that need to be attached to the containers | | saml.volumes | list | `[]` | Configure any additional volumes that need to be attached to the pod | -| scim | object | `{"additionalAnnotations":{},"additionalLabels":{},"customScripts":[],"dnsConfig":{},"dnsPolicy":"","hpa":{"behavior":{},"enabled":true,"maxReplicas":10,"metrics":[],"minReplicas":1,"targetCPUUtilizationPercentage":50},"image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"ghcr.io/janssenproject/jans/scim","tag":"1.1.4_dev"},"lifecycle":{},"livenessProbe":{"httpGet":{"path":"/jans-scim/sys/health-check","port":8080},"initialDelaySeconds":30,"periodSeconds":30,"timeoutSeconds":5},"pdb":{"enabled":true,"maxUnavailable":"90%"},"readinessProbe":{"httpGet":{"path":"/jans-scim/sys/health-check","port":8080},"initialDelaySeconds":25,"periodSeconds":25,"timeoutSeconds":5},"replicas":1,"resources":{"limits":{"cpu":"1000m","memory":"1200Mi"},"requests":{"cpu":"1000m","memory":"1200Mi"}},"service":{"name":"http-scim","port":8080},"topologySpreadConstraints":{},"usrEnvs":{"normal":{},"secret":{}},"volumeMounts":[],"volumes":[]}` | System for Cross-domain Identity Management (SCIM) version 2.0 | +| scim | object | `{"additionalAnnotations":{},"additionalLabels":{},"customScripts":[],"dnsConfig":{},"dnsPolicy":"","hpa":{"behavior":{},"enabled":true,"maxReplicas":10,"metrics":[],"minReplicas":1,"targetCPUUtilizationPercentage":50},"image":{"pullPolicy":"IfNotPresent","pullSecrets":[],"repository":"ghcr.io/janssenproject/jans/scim","tag":"1.1.4-1"},"lifecycle":{},"livenessProbe":{"httpGet":{"path":"/jans-scim/sys/health-check","port":8080},"initialDelaySeconds":30,"periodSeconds":30,"timeoutSeconds":5},"pdb":{"enabled":true,"maxUnavailable":"90%"},"readinessProbe":{"httpGet":{"path":"/jans-scim/sys/health-check","port":8080},"initialDelaySeconds":25,"periodSeconds":25,"timeoutSeconds":5},"replicas":1,"resources":{"limits":{"cpu":"1000m","memory":"1200Mi"},"requests":{"cpu":"1000m","memory":"1200Mi"}},"service":{"name":"http-scim","port":8080},"topologySpreadConstraints":{},"usrEnvs":{"normal":{},"secret":{}},"volumeMounts":[],"volumes":[]}` | System for Cross-domain Identity Management (SCIM) version 2.0 | | scim.additionalAnnotations | object | `{}` | Additional annotations that will be added across the gateway in the format of {cert-manager.io/issuer: "letsencrypt-prod"} | | scim.additionalLabels | object | `{}` | Additional labels that will be added across the gateway in the format of {mylabel: "myapp"} | | scim.customScripts | list | `[]` | Add custom scripts that have been mounted to run before the entrypoint. - /tmp/custom.sh - /tmp/custom2.sh | @@ -618,7 +618,7 @@ Kubernetes: `>=v1.22.0-0` | scim.image.pullPolicy | string | `"IfNotPresent"` | Image pullPolicy to use for deploying. | | scim.image.pullSecrets | list | `[]` | Image Pull Secrets | | scim.image.repository | string | `"ghcr.io/janssenproject/jans/scim"` | Image to use for deploying. | -| scim.image.tag | string | `"1.1.4_dev"` | Image tag to use for deploying. | +| scim.image.tag | string | `"1.1.4-1"` | Image tag to use for deploying. | | scim.livenessProbe | object | `{"httpGet":{"path":"/jans-scim/sys/health-check","port":8080},"initialDelaySeconds":30,"periodSeconds":30,"timeoutSeconds":5}` | Configure the liveness healthcheck for SCIM if needed. | | scim.livenessProbe.httpGet.path | string | `"/jans-scim/sys/health-check"` | http liveness probe endpoint | | scim.pdb | object | `{"enabled":true,"maxUnavailable":"90%"}` | Configure the PodDisruptionBudget | diff --git a/docs/admin/reference/openapi.md b/docs/admin/reference/openapi.md index dd479a06f7d..5761dc6afe3 100644 --- a/docs/admin/reference/openapi.md +++ b/docs/admin/reference/openapi.md @@ -22,7 +22,7 @@ Follow the links below to access respective documentation. | Jans FIDO 2 | [Swagger](https://gluu.org/swagger-ui/?url=https://raw.githubusercontent.com/JanssenProject/jans/vreplace-janssen-version/jans-fido2/docs/jansFido2Swagger.yaml) | | Jans SCIM API | [Swagger](https://gluu.org/swagger-ui/?url=https://raw.githubusercontent.com/JanssenProject/jans/vreplace-janssen-version/jans-scim/server/src/main/resources/jans-scim-openapi.yaml) | | Jans KC SAML API | [Swagger](https://gluu.org/swagger-ui/?url=https://raw.githubusercontent.com/JanssenProject/jans/main/jans-config-api/plugins/docs/kc-saml-plugin-swagger.yaml) | -| Jans Lock Master | [Swagger](https://gluu.org/swagger-ui/?url=https://raw.githubusercontent.com/JanssenProject/jans/main/jans-lock/lock-master.yaml) | +| Jans Lock Master | [Swagger](https://gluu.org/swagger-ui/?url=https://raw.githubusercontent.com/JanssenProject/jans/main/jans-lock/lock-server.yaml) | ## Javadocs diff --git a/jans-auth-server/agama/engine/pom.xml b/jans-auth-server/agama/engine/pom.xml index 3a9892d64ea..993ec03c06e 100644 --- a/jans-auth-server/agama/engine/pom.xml +++ b/jans-auth-server/agama/engine/pom.xml @@ -9,7 +9,7 @@ io.jans jans-auth-server-parent - 1.1.4-SNAPSHOT + 1.1.4 ../../pom.xml @@ -162,6 +162,10 @@ + + io.jans + jans-core-cache + io.jans jans-core-util diff --git a/jans-auth-server/agama/engine/src/main/java/io/jans/agama/engine/page/Page.java b/jans-auth-server/agama/engine/src/main/java/io/jans/agama/engine/page/Page.java index 49b04316f4f..67ae43cad96 100644 --- a/jans-auth-server/agama/engine/src/main/java/io/jans/agama/engine/page/Page.java +++ b/jans-auth-server/agama/engine/src/main/java/io/jans/agama/engine/page/Page.java @@ -10,11 +10,13 @@ import jakarta.inject.Inject; import io.jans.agama.engine.service.WebContext; +import io.jans.service.CacheService; @RequestScoped public class Page { private static final String WEB_CTX_KEY = "webCtx"; + private static final String CACHE_KEY = "cache"; @Inject private WebContext webContext; @@ -24,6 +26,9 @@ public class Page { @Inject private Labels labels; + + @Inject + private CacheService cache; private String templatePath; private Map dataModel; @@ -44,6 +49,7 @@ public Object getDataModel() { dataModel.putIfAbsent(WEB_CTX_KEY, webContext); dataModel.putIfAbsent(Labels.BUNDLE_ID, labels); + dataModel.putIfAbsent(CACHE_KEY, cache); labels.useLocale(webContext.getLocale()); return dataModel; diff --git a/jans-auth-server/agama/engine/src/main/java/io/jans/agama/engine/service/MethodInvoker.java b/jans-auth-server/agama/engine/src/main/java/io/jans/agama/engine/service/MethodInvoker.java index 3af0da2530c..3dacbf97b9f 100644 --- a/jans-auth-server/agama/engine/src/main/java/io/jans/agama/engine/service/MethodInvoker.java +++ b/jans-auth-server/agama/engine/src/main/java/io/jans/agama/engine/service/MethodInvoker.java @@ -174,7 +174,7 @@ because if an interface A extends another interface B, there is no way in Java t List>> entries = new ArrayList<>(); while (current != null) { - logger.debug("Looking up candidate methods in class {}", current.getClass().getName()); + logger.debug("Looking up candidate methods in class {}", current.getName()); for (Method m : current.getDeclaredMethods()) { if (m.getName().equals(methodName) && acceptableExecutable(m, arity, isStatic)) { diff --git a/jans-auth-server/agama/inboundID/pom.xml b/jans-auth-server/agama/inboundID/pom.xml index 51390a12de2..f881f733c9a 100644 --- a/jans-auth-server/agama/inboundID/pom.xml +++ b/jans-auth-server/agama/inboundID/pom.xml @@ -10,7 +10,7 @@ io.jans jans-auth-server-parent - 1.1.4-SNAPSHOT + 1.1.4 ../../pom.xml diff --git a/jans-auth-server/agama/model/pom.xml b/jans-auth-server/agama/model/pom.xml index 502550b9f06..5759d871592 100644 --- a/jans-auth-server/agama/model/pom.xml +++ b/jans-auth-server/agama/model/pom.xml @@ -9,7 +9,7 @@ io.jans jans-auth-server-parent - 1.1.4-SNAPSHOT + 1.1.4 ../../pom.xml diff --git a/jans-auth-server/client/pom.xml b/jans-auth-server/client/pom.xml index ea17efb5e01..e0b23f113c3 100644 --- a/jans-auth-server/client/pom.xml +++ b/jans-auth-server/client/pom.xml @@ -8,7 +8,7 @@ io.jans jans-auth-server-parent - 1.1.4-SNAPSHOT + 1.1.4 @@ -19,7 +19,7 @@ jans-auth-client - ${basedir}/profiles/${cfg}/config-oxauth-test-data.properties + ${basedir}/profiles/${cfg}/config-jans-auth-test-data.properties diff --git a/jans-auth-server/client/profiles/default/config-oxauth-test-data.properties b/jans-auth-server/client/profiles/default/config-jans-auth-test-data.properties similarity index 100% rename from jans-auth-server/client/profiles/default/config-oxauth-test-data.properties rename to jans-auth-server/client/profiles/default/config-jans-auth-test-data.properties diff --git a/jans-auth-server/common/pom.xml b/jans-auth-server/common/pom.xml index fdb382bbd53..4b4f86b1389 100644 --- a/jans-auth-server/common/pom.xml +++ b/jans-auth-server/common/pom.xml @@ -8,7 +8,7 @@ io.jans jans-auth-server-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-auth-server/model/pom.xml b/jans-auth-server/model/pom.xml index 7b2d63d4097..a84d0deb22a 100644 --- a/jans-auth-server/model/pom.xml +++ b/jans-auth-server/model/pom.xml @@ -8,7 +8,7 @@ io.jans jans-auth-server-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-auth-server/persistence-model/pom.xml b/jans-auth-server/persistence-model/pom.xml index cd8e5fc4fdf..0c05f95a6c5 100644 --- a/jans-auth-server/persistence-model/pom.xml +++ b/jans-auth-server/persistence-model/pom.xml @@ -4,7 +4,7 @@ io.jans jans-auth-server-parent - 1.1.4-SNAPSHOT + 1.1.4 jans-auth-persistence-model Persistence model diff --git a/jans-auth-server/pom.xml b/jans-auth-server/pom.xml index 1f9599f457a..fbef26f9513 100644 --- a/jans-auth-server/pom.xml +++ b/jans-auth-server/pom.xml @@ -5,7 +5,7 @@ io.jans jans-auth-server-parent pom - 1.1.4-SNAPSHOT + 1.1.4 Jans authentication server parent diff --git a/jans-auth-server/server-fips/pom.xml b/jans-auth-server/server-fips/pom.xml index 08cea3a48f6..863a56b0fd2 100644 --- a/jans-auth-server/server-fips/pom.xml +++ b/jans-auth-server/server-fips/pom.xml @@ -9,7 +9,7 @@ io.jans jans-auth-server-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-auth-server/server/pom.xml b/jans-auth-server/server/pom.xml index 374d17941c6..c6c59841da3 100644 --- a/jans-auth-server/server/pom.xml +++ b/jans-auth-server/server/pom.xml @@ -8,7 +8,7 @@ io.jans jans-auth-server-parent - 1.1.4-SNAPSHOT + 1.1.4 @@ -20,10 +20,10 @@ profiles/${cfg}/config-build.properties - ${basedir}/profiles/${cfg}/config-oxauth.properties + ${basedir}/profiles/${cfg}/config-jans-auth.properties - ${basedir}/profiles/${cfg}/config-oxauth-test.properties - profiles/${cfg}/config-oxauth-test-data.properties + ${basedir}/profiles/${cfg}/config-jans-auth-test.properties + profiles/${cfg}/config-jans-auth-test-data.properties diff --git a/jans-auth-server/server/profiles/default/config-oxauth-sql.properties b/jans-auth-server/server/profiles/default/config-jans-auth-sql.properties similarity index 100% rename from jans-auth-server/server/profiles/default/config-oxauth-sql.properties rename to jans-auth-server/server/profiles/default/config-jans-auth-sql.properties diff --git a/jans-auth-server/server/profiles/default/config-oxauth-test-data.properties b/jans-auth-server/server/profiles/default/config-jans-auth-test-data.properties similarity index 100% rename from jans-auth-server/server/profiles/default/config-oxauth-test-data.properties rename to jans-auth-server/server/profiles/default/config-jans-auth-test-data.properties diff --git a/jans-auth-server/server/profiles/default/config-oxauth-test.properties b/jans-auth-server/server/profiles/default/config-jans-auth-test.properties similarity index 100% rename from jans-auth-server/server/profiles/default/config-oxauth-test.properties rename to jans-auth-server/server/profiles/default/config-jans-auth-test.properties diff --git a/jans-auth-server/server/profiles/default/config-oxauth.properties b/jans-auth-server/server/profiles/default/config-jans-auth.properties similarity index 100% rename from jans-auth-server/server/profiles/default/config-oxauth.properties rename to jans-auth-server/server/profiles/default/config-jans-auth.properties diff --git a/jans-auth-server/static/pom.xml b/jans-auth-server/static/pom.xml index a91acdb883f..0ca2b907c87 100644 --- a/jans-auth-server/static/pom.xml +++ b/jans-auth-server/static/pom.xml @@ -3,7 +3,7 @@ io.jans jans-auth-static - 1.1.4-SNAPSHOT + 1.1.4 jar jans-auth-static @@ -11,7 +11,7 @@ io.jans jans-auth-server-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-auth-server/test-model/pom.xml b/jans-auth-server/test-model/pom.xml index 909e1ec8835..993f1456b50 100644 --- a/jans-auth-server/test-model/pom.xml +++ b/jans-auth-server/test-model/pom.xml @@ -8,7 +8,7 @@ io.jans jans-auth-server-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-bom/pom.xml b/jans-bom/pom.xml index 6fb53b68f19..954c1dba838 100644 --- a/jans-bom/pom.xml +++ b/jans-bom/pom.xml @@ -5,7 +5,7 @@ jans-bom pom jans-bom - 1.1.4-SNAPSHOT + 1.1.4 @@ -419,7 +419,7 @@ diff --git a/jans-casa/app-fips/pom.xml b/jans-casa/app-fips/pom.xml index 73229743c77..bc41d588632 100644 --- a/jans-casa/app-fips/pom.xml +++ b/jans-casa/app-fips/pom.xml @@ -9,7 +9,7 @@ io.jans casa-base - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-casa/app/pom.xml b/jans-casa/app/pom.xml index 46a65c47323..fc941b4d4bb 100644 --- a/jans-casa/app/pom.xml +++ b/jans-casa/app/pom.xml @@ -9,7 +9,7 @@ io.jans casa-base - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-casa/config/pom.xml b/jans-casa/config/pom.xml index 40adcc4f646..e32d294ae52 100644 --- a/jans-casa/config/pom.xml +++ b/jans-casa/config/pom.xml @@ -9,7 +9,7 @@ io.jans casa-base - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-casa/plugins/acct-linking/pom.xml b/jans-casa/plugins/acct-linking/pom.xml index e8db285d479..f2266ff46cd 100644 --- a/jans-casa/plugins/acct-linking/pom.xml +++ b/jans-casa/plugins/acct-linking/pom.xml @@ -5,7 +5,7 @@ io.jans.casa.plugins ${plugin.id} - 1.1.4-SNAPSHOT + 1.1.4 jar diff --git a/jans-casa/plugins/bioid/pom.xml b/jans-casa/plugins/bioid/pom.xml index 87ae7b55c60..e25be40be36 100644 --- a/jans-casa/plugins/bioid/pom.xml +++ b/jans-casa/plugins/bioid/pom.xml @@ -5,7 +5,7 @@ io.jans.casa.plugins ${plugin.id} - 1.1.4-SNAPSHOT + 1.1.4 jar diff --git a/jans-casa/plugins/client-authorizations/pom.xml b/jans-casa/plugins/client-authorizations/pom.xml index a4cb5daf662..1c3e046991a 100644 --- a/jans-casa/plugins/client-authorizations/pom.xml +++ b/jans-casa/plugins/client-authorizations/pom.xml @@ -5,7 +5,7 @@ io.jans.casa.plugins ${plugin.id} - 1.1.4-SNAPSHOT + 1.1.4 jar diff --git a/jans-casa/plugins/custom-branding/pom.xml b/jans-casa/plugins/custom-branding/pom.xml index 80778437189..c5ccc20bda8 100644 --- a/jans-casa/plugins/custom-branding/pom.xml +++ b/jans-casa/plugins/custom-branding/pom.xml @@ -5,7 +5,7 @@ io.jans.casa.plugins ${plugin.id} - 1.1.4-SNAPSHOT + 1.1.4 jar diff --git a/jans-casa/plugins/email_2fa_core/pom.xml b/jans-casa/plugins/email_2fa_core/pom.xml index 68f410ea5b4..aeebfa0523c 100644 --- a/jans-casa/plugins/email_2fa_core/pom.xml +++ b/jans-casa/plugins/email_2fa_core/pom.xml @@ -5,7 +5,7 @@ io.jans.casa.plugins ${plugin.id} - 1.1.4-SNAPSHOT + 1.1.4 jar diff --git a/jans-casa/plugins/samples/authentication-script-properties/pom.xml b/jans-casa/plugins/samples/authentication-script-properties/pom.xml index a4bab293cc7..a2850c5e4ac 100644 --- a/jans-casa/plugins/samples/authentication-script-properties/pom.xml +++ b/jans-casa/plugins/samples/authentication-script-properties/pom.xml @@ -5,7 +5,7 @@ co.acme ${plugin.id} - 1.1.4-SNAPSHOT + 1.1.4 jar diff --git a/jans-casa/plugins/samples/helloworld/pom.xml b/jans-casa/plugins/samples/helloworld/pom.xml index d7a84b5821a..54667309ebb 100644 --- a/jans-casa/plugins/samples/helloworld/pom.xml +++ b/jans-casa/plugins/samples/helloworld/pom.xml @@ -5,7 +5,7 @@ co.acme ${plugin.id} - 1.1.4-SNAPSHOT + 1.1.4 jar diff --git a/jans-casa/plugins/samples/sample-cred/pom.xml b/jans-casa/plugins/samples/sample-cred/pom.xml index d5b4b50bc45..89644265409 100644 --- a/jans-casa/plugins/samples/sample-cred/pom.xml +++ b/jans-casa/plugins/samples/sample-cred/pom.xml @@ -5,7 +5,7 @@ io.jans.casa.plugins ${plugin.id} - 1.1.4-SNAPSHOT + 1.1.4 jar diff --git a/jans-casa/plugins/strong-authn-settings/pom.xml b/jans-casa/plugins/strong-authn-settings/pom.xml index d0284f7e5d2..8d4f6517b50 100644 --- a/jans-casa/plugins/strong-authn-settings/pom.xml +++ b/jans-casa/plugins/strong-authn-settings/pom.xml @@ -5,7 +5,7 @@ io.jans.casa.plugins ${plugin.id} - 1.1.4-SNAPSHOT + 1.1.4 jar diff --git a/jans-casa/pom.xml b/jans-casa/pom.xml index 7533430c99a..e59be35d2b0 100644 --- a/jans-casa/pom.xml +++ b/jans-casa/pom.xml @@ -5,7 +5,7 @@ io.jans casa-base - 1.1.4-SNAPSHOT + 1.1.4 pom diff --git a/jans-casa/shared/pom.xml b/jans-casa/shared/pom.xml index 0bbf8f22335..ad3a0f998a7 100644 --- a/jans-casa/shared/pom.xml +++ b/jans-casa/shared/pom.xml @@ -9,7 +9,7 @@ io.jans casa-base - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-cli-tui/cli_tui/version.py b/jans-cli-tui/cli_tui/version.py index f17a550451e..018b580bebb 100644 --- a/jans-cli-tui/cli_tui/version.py +++ b/jans-cli-tui/cli_tui/version.py @@ -3,4 +3,4 @@ https://www.apache.org/licenses/LICENSE-2.0 """ -__version__ = "1.1.4-dev" +__version__ = "1.1.4" diff --git a/jans-config-api/common/pom.xml b/jans-config-api/common/pom.xml index f3c34812ed5..c6c215a8c02 100644 --- a/jans-config-api/common/pom.xml +++ b/jans-config-api/common/pom.xml @@ -9,7 +9,7 @@ io.jans jans-config-api-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-config-api/plugins/admin-ui-plugin/pom.xml b/jans-config-api/plugins/admin-ui-plugin/pom.xml index a4469167e43..b1359f27559 100644 --- a/jans-config-api/plugins/admin-ui-plugin/pom.xml +++ b/jans-config-api/plugins/admin-ui-plugin/pom.xml @@ -3,7 +3,7 @@ plugins io.jans.jans-config-api.plugins - 1.1.4-SNAPSHOT + 1.1.4 4.0.0 diff --git a/jans-config-api/plugins/fido2-plugin/pom.xml b/jans-config-api/plugins/fido2-plugin/pom.xml index e7f95379089..06bffa9cb14 100644 --- a/jans-config-api/plugins/fido2-plugin/pom.xml +++ b/jans-config-api/plugins/fido2-plugin/pom.xml @@ -3,7 +3,7 @@ plugins io.jans.jans-config-api.plugins - 1.1.4-SNAPSHOT + 1.1.4 4.0.0 fido2-plugin diff --git a/jans-config-api/plugins/jans-link-plugin/pom.xml b/jans-config-api/plugins/jans-link-plugin/pom.xml index d54ea272007..8c74c6ec414 100644 --- a/jans-config-api/plugins/jans-link-plugin/pom.xml +++ b/jans-config-api/plugins/jans-link-plugin/pom.xml @@ -3,7 +3,7 @@ plugins io.jans.jans-config-api.plugins - 1.1.4-SNAPSHOT + 1.1.4 4.0.0 jans-link-plugin diff --git a/jans-config-api/plugins/kc-link-plugin/pom.xml b/jans-config-api/plugins/kc-link-plugin/pom.xml index eab9ef077f7..5e431cbd224 100644 --- a/jans-config-api/plugins/kc-link-plugin/pom.xml +++ b/jans-config-api/plugins/kc-link-plugin/pom.xml @@ -5,7 +5,7 @@ plugins io.jans.jans-config-api.plugins - 1.1.4-SNAPSHOT + 1.1.4 4.0.0 diff --git a/jans-config-api/plugins/kc-saml-plugin/pom.xml b/jans-config-api/plugins/kc-saml-plugin/pom.xml index 8dde6c2e9af..c6328e513b9 100644 --- a/jans-config-api/plugins/kc-saml-plugin/pom.xml +++ b/jans-config-api/plugins/kc-saml-plugin/pom.xml @@ -5,7 +5,7 @@ plugins io.jans.jans-config-api.plugins - 1.1.4-SNAPSHOT + 1.1.4 4.0.0 diff --git a/jans-config-api/plugins/lock-plugin/pom.xml b/jans-config-api/plugins/lock-plugin/pom.xml index 3eca7ef1f14..ec227b4349e 100644 --- a/jans-config-api/plugins/lock-plugin/pom.xml +++ b/jans-config-api/plugins/lock-plugin/pom.xml @@ -5,7 +5,7 @@ plugins io.jans.jans-config-api.plugins - 1.1.4-SNAPSHOT + 1.1.4 4.0.0 diff --git a/jans-config-api/plugins/pom.xml b/jans-config-api/plugins/pom.xml index 86455172dcc..e50fc9f8ed1 100644 --- a/jans-config-api/plugins/pom.xml +++ b/jans-config-api/plugins/pom.xml @@ -4,14 +4,14 @@ io.jans jans-config-api-parent - 1.1.4-SNAPSHOT + 1.1.4 4.0.0 io.jans.jans-config-api.plugins plugins - 1.1.4-SNAPSHOT + 1.1.4 pom diff --git a/jans-config-api/plugins/sample/demo/pom.xml b/jans-config-api/plugins/sample/demo/pom.xml index 69c1808a001..507e645b756 100644 --- a/jans-config-api/plugins/sample/demo/pom.xml +++ b/jans-config-api/plugins/sample/demo/pom.xml @@ -3,7 +3,7 @@ io.jans.jans-config-api.plugins ${plugin.id} - 1.1.4-SNAPSHOT + 1.1.4 jar demo diff --git a/jans-config-api/plugins/sample/helloworld/pom.xml b/jans-config-api/plugins/sample/helloworld/pom.xml index f565d04742d..8a71e222eec 100644 --- a/jans-config-api/plugins/sample/helloworld/pom.xml +++ b/jans-config-api/plugins/sample/helloworld/pom.xml @@ -3,7 +3,7 @@ com.spl ${plugin.id} - 1.1.4-SNAPSHOT + 1.1.4 jar helloworld diff --git a/jans-config-api/plugins/scim-plugin/pom.xml b/jans-config-api/plugins/scim-plugin/pom.xml index bbb1453dfc8..9e5105ca5da 100644 --- a/jans-config-api/plugins/scim-plugin/pom.xml +++ b/jans-config-api/plugins/scim-plugin/pom.xml @@ -3,7 +3,7 @@ plugins io.jans.jans-config-api.plugins - 1.1.4-SNAPSHOT + 1.1.4 4.0.0 scim-plugin diff --git a/jans-config-api/plugins/user-mgt-plugin/pom.xml b/jans-config-api/plugins/user-mgt-plugin/pom.xml index e890655aa5d..736a59141a2 100644 --- a/jans-config-api/plugins/user-mgt-plugin/pom.xml +++ b/jans-config-api/plugins/user-mgt-plugin/pom.xml @@ -3,7 +3,7 @@ plugins io.jans.jans-config-api.plugins - 1.1.4-SNAPSHOT + 1.1.4 4.0.0 user-mgt-plugin diff --git a/jans-config-api/pom.xml b/jans-config-api/pom.xml index 783095ab0d8..8c1096866d6 100644 --- a/jans-config-api/pom.xml +++ b/jans-config-api/pom.xml @@ -5,7 +5,7 @@ io.jans jans-config-api-parent pom - 1.1.4-SNAPSHOT + 1.1.4 jans-config-api-parent diff --git a/jans-config-api/server-fips/pom.xml b/jans-config-api/server-fips/pom.xml index 3accb1589a8..8913cd8e886 100644 --- a/jans-config-api/server-fips/pom.xml +++ b/jans-config-api/server-fips/pom.xml @@ -9,7 +9,7 @@ io.jans jans-config-api-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-config-api/server/pom.xml b/jans-config-api/server/pom.xml index 04768957cad..1ea12505530 100644 --- a/jans-config-api/server/pom.xml +++ b/jans-config-api/server/pom.xml @@ -9,7 +9,7 @@ io.jans jans-config-api-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-config-api/shared/pom.xml b/jans-config-api/shared/pom.xml index 7f54f1ab9ac..3599e23d48a 100644 --- a/jans-config-api/shared/pom.xml +++ b/jans-config-api/shared/pom.xml @@ -7,7 +7,7 @@ io.jans jans-config-api-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-core/cache/pom.xml b/jans-core/cache/pom.xml index 974b672c6be..d41562dabb7 100644 --- a/jans-core/cache/pom.xml +++ b/jans-core/cache/pom.xml @@ -7,7 +7,7 @@ io.jans jans-core-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-core/cdi/pom.xml b/jans-core/cdi/pom.xml index 03c284b3029..7ab0f0f89e1 100644 --- a/jans-core/cdi/pom.xml +++ b/jans-core/cdi/pom.xml @@ -8,7 +8,7 @@ io.jans jans-core-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-core/demo-cdi/pom.xml b/jans-core/demo-cdi/pom.xml index 91b65ff6aa5..2dbe740adef 100644 --- a/jans-core/demo-cdi/pom.xml +++ b/jans-core/demo-cdi/pom.xml @@ -7,7 +7,7 @@ io.jans jans-core-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-core/doc/pom.xml b/jans-core/doc/pom.xml index 2d4a59e418f..d68d4628b68 100644 --- a/jans-core/doc/pom.xml +++ b/jans-core/doc/pom.xml @@ -3,7 +3,7 @@ jans-core-parent io.jans - 1.1.4-SNAPSHOT + 1.1.4 4.0.0 diff --git a/jans-core/document-store/pom.xml b/jans-core/document-store/pom.xml index 68fa8642cfd..d2f89caf129 100644 --- a/jans-core/document-store/pom.xml +++ b/jans-core/document-store/pom.xml @@ -7,7 +7,7 @@ io.jans jans-core-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-core/exception-extension-cdi/pom.xml b/jans-core/exception-extension-cdi/pom.xml index 4fd4ab23d2a..53d20d34555 100644 --- a/jans-core/exception-extension-cdi/pom.xml +++ b/jans-core/exception-extension-cdi/pom.xml @@ -8,7 +8,7 @@ io.jans jans-core-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-core/java-ext/pom.xml b/jans-core/java-ext/pom.xml index 13279835499..0117ab4839c 100644 --- a/jans-core/java-ext/pom.xml +++ b/jans-core/java-ext/pom.xml @@ -8,7 +8,7 @@ io.jans jans-core-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-core/jsf-util/pom.xml b/jans-core/jsf-util/pom.xml index 606b2a6b5ae..23a39dca15f 100644 --- a/jans-core/jsf-util/pom.xml +++ b/jans-core/jsf-util/pom.xml @@ -9,7 +9,7 @@ io.jans jans-core-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-core/message/pom.xml b/jans-core/message/pom.xml index d1f7c2126d0..35c011b11b7 100644 --- a/jans-core/message/pom.xml +++ b/jans-core/message/pom.xml @@ -7,7 +7,7 @@ io.jans jans-core-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-core/model/pom.xml b/jans-core/model/pom.xml index fb4b3025394..6e2da311f23 100644 --- a/jans-core/model/pom.xml +++ b/jans-core/model/pom.xml @@ -8,7 +8,7 @@ io.jans jans-core-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-core/notify-client/pom.xml b/jans-core/notify-client/pom.xml index b3d504d66aa..8c9bd99f385 100644 --- a/jans-core/notify-client/pom.xml +++ b/jans-core/notify-client/pom.xml @@ -9,7 +9,7 @@ io.jans jans-core-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-core/pom.xml b/jans-core/pom.xml index 788cc8e89a6..acaf33f124e 100644 --- a/jans-core/pom.xml +++ b/jans-core/pom.xml @@ -3,7 +3,7 @@ io.jans jans-core-parent pom - 1.1.4-SNAPSHOT + 1.1.4 jans-core diff --git a/jans-core/radius/pom.xml b/jans-core/radius/pom.xml index 5a5efd5a4a2..95817acce46 100644 --- a/jans-core/radius/pom.xml +++ b/jans-core/radius/pom.xml @@ -8,7 +8,7 @@ io.jans jans-core-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-core/saml/pom.xml b/jans-core/saml/pom.xml index 68dbd2e9a04..ef3fc1bafb8 100644 --- a/jans-core/saml/pom.xml +++ b/jans-core/saml/pom.xml @@ -8,7 +8,7 @@ io.jans jans-core-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-core/saml/src/pom.xml b/jans-core/saml/src/pom.xml index 92579a6128a..cbd29bb6147 100644 --- a/jans-core/saml/src/pom.xml +++ b/jans-core/saml/src/pom.xml @@ -8,7 +8,7 @@ io.jans jans-core-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-core/script/pom.xml b/jans-core/script/pom.xml index 8d6efb21dc5..4364b2601c0 100644 --- a/jans-core/script/pom.xml +++ b/jans-core/script/pom.xml @@ -8,7 +8,7 @@ io.jans jans-core-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-core/security-extension-cdi/pom.xml b/jans-core/security-extension-cdi/pom.xml index d09279d191d..1616977ea14 100644 --- a/jans-core/security-extension-cdi/pom.xml +++ b/jans-core/security-extension-cdi/pom.xml @@ -8,7 +8,7 @@ io.jans jans-core-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-core/server/pom.xml b/jans-core/server/pom.xml index 12f2e532986..d7949ebb7b9 100644 --- a/jans-core/server/pom.xml +++ b/jans-core/server/pom.xml @@ -8,7 +8,7 @@ io.jans jans-core-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-core/service/pom.xml b/jans-core/service/pom.xml index a149a659daa..3c370e6356d 100644 --- a/jans-core/service/pom.xml +++ b/jans-core/service/pom.xml @@ -8,7 +8,7 @@ io.jans jans-core-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-core/standalone/pom.xml b/jans-core/standalone/pom.xml index aa7abe434f9..b4619716fd2 100644 --- a/jans-core/standalone/pom.xml +++ b/jans-core/standalone/pom.xml @@ -7,7 +7,7 @@ io.jans jans-core-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-core/timer-weld/pom.xml b/jans-core/timer-weld/pom.xml index d5cb648e143..70483296e5b 100644 --- a/jans-core/timer-weld/pom.xml +++ b/jans-core/timer-weld/pom.xml @@ -7,7 +7,7 @@ io.jans jans-core-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-core/uma-rs-core/pom.xml b/jans-core/uma-rs-core/pom.xml index 0155bc7c29e..670e2172382 100644 --- a/jans-core/uma-rs-core/pom.xml +++ b/jans-core/uma-rs-core/pom.xml @@ -9,7 +9,7 @@ io.jans jans-core-parent - 1.1.4-SNAPSHOT + 1.1.4 true diff --git a/jans-core/util/pom.xml b/jans-core/util/pom.xml index 31bc8a85e47..803b8347678 100644 --- a/jans-core/util/pom.xml +++ b/jans-core/util/pom.xml @@ -8,7 +8,7 @@ io.jans jans-core-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-fido2/client/pom.xml b/jans-fido2/client/pom.xml index 64467ee92a1..43a0138979c 100644 --- a/jans-fido2/client/pom.xml +++ b/jans-fido2/client/pom.xml @@ -9,7 +9,7 @@ io.jans jans-fido2-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-fido2/model/pom.xml b/jans-fido2/model/pom.xml index 4a3a4abea91..dfd389c18d9 100644 --- a/jans-fido2/model/pom.xml +++ b/jans-fido2/model/pom.xml @@ -10,7 +10,7 @@ io.jans jans-fido2-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-fido2/pom.xml b/jans-fido2/pom.xml index 50991d42ca7..f4d9772aa22 100644 --- a/jans-fido2/pom.xml +++ b/jans-fido2/pom.xml @@ -5,7 +5,7 @@ io.jans jans-fido2-parent pom - 1.1.4-SNAPSHOT + 1.1.4 Fido2 API diff --git a/jans-fido2/server-fips/pom.xml b/jans-fido2/server-fips/pom.xml index 8acd6cdc365..9e5eabb5664 100644 --- a/jans-fido2/server-fips/pom.xml +++ b/jans-fido2/server-fips/pom.xml @@ -9,7 +9,7 @@ io.jans jans-fido2-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-fido2/server/pom.xml b/jans-fido2/server/pom.xml index 0e7b4272dab..2a6597be210 100644 --- a/jans-fido2/server/pom.xml +++ b/jans-fido2/server/pom.xml @@ -9,7 +9,7 @@ io.jans jans-fido2-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-keycloak-integration/job-scheduler/pom.xml b/jans-keycloak-integration/job-scheduler/pom.xml index a86495adbe0..bd8c2e3bd50 100644 --- a/jans-keycloak-integration/job-scheduler/pom.xml +++ b/jans-keycloak-integration/job-scheduler/pom.xml @@ -9,7 +9,7 @@ io.jans jans-kc-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-keycloak-integration/pom.xml b/jans-keycloak-integration/pom.xml index 8c78c3fffa2..0af3e7b5806 100644 --- a/jans-keycloak-integration/pom.xml +++ b/jans-keycloak-integration/pom.xml @@ -4,7 +4,7 @@ io.jans jans-kc-parent pom - 1.1.4-SNAPSHOT + 1.1.4 keycloak-integration-parent diff --git a/jans-keycloak-integration/spi/pom.xml b/jans-keycloak-integration/spi/pom.xml index 7fba12e30f1..ab85c04a386 100644 --- a/jans-keycloak-integration/spi/pom.xml +++ b/jans-keycloak-integration/spi/pom.xml @@ -9,7 +9,7 @@ io.jans jans-kc-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-keycloak-link/model/pom.xml b/jans-keycloak-link/model/pom.xml index 0e4ce97de25..c2d86f9ef2a 100644 --- a/jans-keycloak-link/model/pom.xml +++ b/jans-keycloak-link/model/pom.xml @@ -2,7 +2,7 @@ jans-keycloak-link-parent io.jans - 1.1.4-SNAPSHOT + 1.1.4 4.0.0 jans-keycloak-link-model diff --git a/jans-keycloak-link/model/src/main/resources/archetype-resources/pom.xml b/jans-keycloak-link/model/src/main/resources/archetype-resources/pom.xml index 22a9c00edef..20d147cca0f 100644 --- a/jans-keycloak-link/model/src/main/resources/archetype-resources/pom.xml +++ b/jans-keycloak-link/model/src/main/resources/archetype-resources/pom.xml @@ -2,7 +2,7 @@ 4.0.0 $io.jans $model - 1.1.4-SNAPSHOT + 1.1.4 junit diff --git a/jans-keycloak-link/pom.xml b/jans-keycloak-link/pom.xml index a7605143517..b3ee50ec37c 100644 --- a/jans-keycloak-link/pom.xml +++ b/jans-keycloak-link/pom.xml @@ -2,7 +2,7 @@ 4.0.0 io.jans jans-keycloak-link-parent - 1.1.4-SNAPSHOT + 1.1.4 model service diff --git a/jans-keycloak-link/server/pom.xml b/jans-keycloak-link/server/pom.xml index 6d8070f3376..26a1e54a4e5 100644 --- a/jans-keycloak-link/server/pom.xml +++ b/jans-keycloak-link/server/pom.xml @@ -2,7 +2,7 @@ jans-keycloak-link-parent io.jans - 1.1.4-SNAPSHOT + 1.1.4 4.0.0 jans-keycloak-link-server diff --git a/jans-keycloak-link/service/pom.xml b/jans-keycloak-link/service/pom.xml index 1aa6173256e..7d49a88ff16 100644 --- a/jans-keycloak-link/service/pom.xml +++ b/jans-keycloak-link/service/pom.xml @@ -2,7 +2,7 @@ jans-keycloak-link-parent io.jans - 1.1.4-SNAPSHOT + 1.1.4 4.0.0 diff --git a/jans-link/model/pom.xml b/jans-link/model/pom.xml index 0ad96866472..f656852c99d 100644 --- a/jans-link/model/pom.xml +++ b/jans-link/model/pom.xml @@ -2,7 +2,7 @@ jans-link-server-parent io.jans - 1.1.4-SNAPSHOT + 1.1.4 4.0.0 jans-link-model diff --git a/jans-link/pom.xml b/jans-link/pom.xml index ee94675709c..e0d37fe0d48 100644 --- a/jans-link/pom.xml +++ b/jans-link/pom.xml @@ -2,7 +2,7 @@ 4.0.0 io.jans jans-link-server-parent - 1.1.4-SNAPSHOT + 1.1.4 model service diff --git a/jans-link/server-fips/pom.xml b/jans-link/server-fips/pom.xml index 8bc7408cdb1..39a99165007 100644 --- a/jans-link/server-fips/pom.xml +++ b/jans-link/server-fips/pom.xml @@ -9,7 +9,7 @@ jans-link-server-parent io.jans - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-link/server/pom.xml b/jans-link/server/pom.xml index 8b028b6ea48..3bc1d6c2645 100644 --- a/jans-link/server/pom.xml +++ b/jans-link/server/pom.xml @@ -2,7 +2,7 @@ jans-link-server-parent io.jans - 1.1.4-SNAPSHOT + 1.1.4 4.0.0 jans-link-server diff --git a/jans-link/service/pom.xml b/jans-link/service/pom.xml index 1221a364f0d..e21d65e8974 100644 --- a/jans-link/service/pom.xml +++ b/jans-link/service/pom.xml @@ -2,7 +2,7 @@ jans-link-server-parent io.jans - 1.1.4-SNAPSHOT + 1.1.4 4.0.0 jans-link-service diff --git a/jans-linux-setup/jans_setup/app_info.json b/jans-linux-setup/jans_setup/app_info.json index 0b0031a02c2..4d084f62601 100644 --- a/jans-linux-setup/jans_setup/app_info.json +++ b/jans-linux-setup/jans_setup/app_info.json @@ -1,6 +1,6 @@ { "JANS_APP_VERSION": "1.1.4", - "JANS_BUILD": "-SNAPSHOT", + "JANS_BUILD": "", "JETTY_VERSION": "11.0.15", "AMAZON_CORRETTO_VERSION": "17", "JYTHON_VERSION": "2.7.3", diff --git a/jans-linux-setup/jans_setup/setup_app/version.py b/jans-linux-setup/jans_setup/setup_app/version.py index b723cc41217..c72e3798a10 100644 --- a/jans-linux-setup/jans_setup/setup_app/version.py +++ b/jans-linux-setup/jans_setup/setup_app/version.py @@ -1 +1 @@ -__version__ = "1.1.4-dev" +__version__ = "1.1.4" diff --git a/jans-lock/lock-server/client/pom.xml b/jans-lock/lock-server/client/pom.xml index 22a243e3677..b8396c553a9 100644 --- a/jans-lock/lock-server/client/pom.xml +++ b/jans-lock/lock-server/client/pom.xml @@ -11,7 +11,7 @@ jans-lock-server-parent io.jans - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-lock/lock-server/model/pom.xml b/jans-lock/lock-server/model/pom.xml index 93e2f88ddc7..1fcf3f7c32c 100644 --- a/jans-lock/lock-server/model/pom.xml +++ b/jans-lock/lock-server/model/pom.xml @@ -10,7 +10,7 @@ jans-lock-server-parent io.jans - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-lock/lock-server/pom.xml b/jans-lock/lock-server/pom.xml index 2e032ab478f..0d0b5c2acf7 100644 --- a/jans-lock/lock-server/pom.xml +++ b/jans-lock/lock-server/pom.xml @@ -4,7 +4,7 @@ 4.0.0 io.jans jans-lock-server-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-lock/lock-server/server-fips/pom.xml b/jans-lock/lock-server/server-fips/pom.xml index a6b5bfd234e..1a5e4d699fb 100644 --- a/jans-lock/lock-server/server-fips/pom.xml +++ b/jans-lock/lock-server/server-fips/pom.xml @@ -9,7 +9,7 @@ jans-lock-server-parent io.jans - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-lock/lock-server/server/pom.xml b/jans-lock/lock-server/server/pom.xml index 0222b1ead55..a2a361f884b 100644 --- a/jans-lock/lock-server/server/pom.xml +++ b/jans-lock/lock-server/server/pom.xml @@ -6,7 +6,7 @@ jans-lock-server-parent io.jans - 1.1.4-SNAPSHOT + 1.1.4 4.0.0 diff --git a/jans-lock/lock-server/service/pom.xml b/jans-lock/lock-server/service/pom.xml index 3135437c7ae..580c7b29f30 100644 --- a/jans-lock/lock-server/service/pom.xml +++ b/jans-lock/lock-server/service/pom.xml @@ -5,7 +5,7 @@ jans-lock-server-parent io.jans - 1.1.4-SNAPSHOT + 1.1.4 4.0.0 diff --git a/jans-orm/annotation/pom.xml b/jans-orm/annotation/pom.xml index ca546763c94..01155e3f19e 100644 --- a/jans-orm/annotation/pom.xml +++ b/jans-orm/annotation/pom.xml @@ -8,6 +8,6 @@ io.jans jans-orm-parent - 1.1.4-SNAPSHOT + 1.1.4 \ No newline at end of file diff --git a/jans-orm/cdi/pom.xml b/jans-orm/cdi/pom.xml index 46503c87683..b8e17050777 100644 --- a/jans-orm/cdi/pom.xml +++ b/jans-orm/cdi/pom.xml @@ -7,7 +7,7 @@ io.jans jans-orm-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-orm/core/pom.xml b/jans-orm/core/pom.xml index 3cef5aa6ce8..ca74dd4d010 100644 --- a/jans-orm/core/pom.xml +++ b/jans-orm/core/pom.xml @@ -8,7 +8,7 @@ io.jans jans-orm-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-orm/couchbase-libs/pom.xml b/jans-orm/couchbase-libs/pom.xml index a72adebc69f..39b5d1aa147 100644 --- a/jans-orm/couchbase-libs/pom.xml +++ b/jans-orm/couchbase-libs/pom.xml @@ -8,7 +8,7 @@ io.jans jans-orm-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-orm/couchbase-sample/pom.xml b/jans-orm/couchbase-sample/pom.xml index 8681491127c..9358c55eb33 100644 --- a/jans-orm/couchbase-sample/pom.xml +++ b/jans-orm/couchbase-sample/pom.xml @@ -8,7 +8,7 @@ io.jans jans-orm-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-orm/couchbase/pom.xml b/jans-orm/couchbase/pom.xml index e4c724deeaa..8f96a1cafbd 100644 --- a/jans-orm/couchbase/pom.xml +++ b/jans-orm/couchbase/pom.xml @@ -8,7 +8,7 @@ io.jans jans-orm-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-orm/filter/pom.xml b/jans-orm/filter/pom.xml index e1a2dabe575..b98720e0e84 100644 --- a/jans-orm/filter/pom.xml +++ b/jans-orm/filter/pom.xml @@ -8,7 +8,7 @@ io.jans jans-orm-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-orm/hybrid/pom.xml b/jans-orm/hybrid/pom.xml index ba91de292c8..8b45dd15305 100644 --- a/jans-orm/hybrid/pom.xml +++ b/jans-orm/hybrid/pom.xml @@ -8,7 +8,7 @@ io.jans jans-orm-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-orm/ldap-sample/pom.xml b/jans-orm/ldap-sample/pom.xml index 9d4e7afdfdf..311c5047696 100644 --- a/jans-orm/ldap-sample/pom.xml +++ b/jans-orm/ldap-sample/pom.xml @@ -8,7 +8,7 @@ io.jans jans-orm-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-orm/ldap/pom.xml b/jans-orm/ldap/pom.xml index 35788f14e43..919429b8184 100644 --- a/jans-orm/ldap/pom.xml +++ b/jans-orm/ldap/pom.xml @@ -8,7 +8,7 @@ io.jans jans-orm-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-orm/model/pom.xml b/jans-orm/model/pom.xml index 8094abbe1e4..e26c9a9168e 100644 --- a/jans-orm/model/pom.xml +++ b/jans-orm/model/pom.xml @@ -8,7 +8,7 @@ io.jans jans-orm-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-orm/pom.xml b/jans-orm/pom.xml index 765466bacee..782460343c4 100644 --- a/jans-orm/pom.xml +++ b/jans-orm/pom.xml @@ -3,7 +3,7 @@ io.jans jans-orm-parent pom - 1.1.4-SNAPSHOT + 1.1.4 orm diff --git a/jans-orm/spanner-libs/pom.xml b/jans-orm/spanner-libs/pom.xml index de35fa76821..2c037efb72d 100644 --- a/jans-orm/spanner-libs/pom.xml +++ b/jans-orm/spanner-libs/pom.xml @@ -8,7 +8,7 @@ io.jans jans-orm-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-orm/spanner-sample/pom.xml b/jans-orm/spanner-sample/pom.xml index b6941daa045..662b157fef0 100644 --- a/jans-orm/spanner-sample/pom.xml +++ b/jans-orm/spanner-sample/pom.xml @@ -8,7 +8,7 @@ io.jans jans-orm-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-orm/spanner/pom.xml b/jans-orm/spanner/pom.xml index b1e130ae307..6aba06a97f4 100644 --- a/jans-orm/spanner/pom.xml +++ b/jans-orm/spanner/pom.xml @@ -8,7 +8,7 @@ io.jans jans-orm-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-orm/sql-sample/pom.xml b/jans-orm/sql-sample/pom.xml index cb666900bc9..41bd902c504 100644 --- a/jans-orm/sql-sample/pom.xml +++ b/jans-orm/sql-sample/pom.xml @@ -8,7 +8,7 @@ io.jans jans-orm-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-orm/sql/pom.xml b/jans-orm/sql/pom.xml index c5bee6a8272..ba9b1e05bce 100644 --- a/jans-orm/sql/pom.xml +++ b/jans-orm/sql/pom.xml @@ -8,7 +8,7 @@ io.jans jans-orm-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-orm/standalone/pom.xml b/jans-orm/standalone/pom.xml index 8c5fbf5f0e4..24daefd369f 100644 --- a/jans-orm/standalone/pom.xml +++ b/jans-orm/standalone/pom.xml @@ -7,7 +7,7 @@ io.jans jans-orm-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-orm/util/pom.xml b/jans-orm/util/pom.xml index b0fa8fb9621..8788c7e4d4c 100644 --- a/jans-orm/util/pom.xml +++ b/jans-orm/util/pom.xml @@ -8,7 +8,7 @@ io.jans jans-orm-parent - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-pycloudlib/jans/pycloudlib/version.py b/jans-pycloudlib/jans/pycloudlib/version.py index 95cad2e6974..ad26d346d8b 100644 --- a/jans-pycloudlib/jans/pycloudlib/version.py +++ b/jans-pycloudlib/jans/pycloudlib/version.py @@ -1,3 +1,3 @@ """This module contains version-related info.""" -__version__ = "1.1.4-dev" # pragma: no cover +__version__ = "1.1.4" # pragma: no cover diff --git a/jans-scim/client/pom.xml b/jans-scim/client/pom.xml index d12b4d7c5b6..042194f7273 100644 --- a/jans-scim/client/pom.xml +++ b/jans-scim/client/pom.xml @@ -10,7 +10,7 @@ io.jans jans-scim - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-scim/model/pom.xml b/jans-scim/model/pom.xml index 0999eb838a5..debc6a0db59 100644 --- a/jans-scim/model/pom.xml +++ b/jans-scim/model/pom.xml @@ -10,7 +10,7 @@ io.jans jans-scim - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-scim/pom.xml b/jans-scim/pom.xml index 0d197aefd52..4a0a19af6c4 100644 --- a/jans-scim/pom.xml +++ b/jans-scim/pom.xml @@ -5,7 +5,7 @@ io.jans jans-scim pom - 1.1.4-SNAPSHOT + 1.1.4 SCIM API http://www.gluu.org diff --git a/jans-scim/server-fips/pom.xml b/jans-scim/server-fips/pom.xml index 6b783703177..efbe7425cee 100644 --- a/jans-scim/server-fips/pom.xml +++ b/jans-scim/server-fips/pom.xml @@ -9,7 +9,7 @@ io.jans jans-scim - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-scim/server/pom.xml b/jans-scim/server/pom.xml index 5307e4f09ee..f05afad4c7f 100644 --- a/jans-scim/server/pom.xml +++ b/jans-scim/server/pom.xml @@ -10,7 +10,7 @@ io.jans jans-scim - 1.1.4-SNAPSHOT + 1.1.4 diff --git a/jans-scim/service/pom.xml b/jans-scim/service/pom.xml index df4880aac73..73f392ad3f3 100644 --- a/jans-scim/service/pom.xml +++ b/jans-scim/service/pom.xml @@ -8,7 +8,7 @@ io.jans jans-scim - 1.1.4-SNAPSHOT + 1.1.4