Summary:

The code changes in this pull request are primarily focused on updates to the documentation and configuration for the Janssen (or Gluu flex) server deployment using Docker Compose and Kubernetes Helm charts. The changes include updates to environment variables, test client configurations, and version upgrades for the Janssen microservices.

From an application security perspective, the key points to consider are:

1. Ensuring that all environment variables and configurations are properly secured and not exposed in the production environment.
2. Verifying that the test client credentials are not used in the production environment.
3. Reviewing the security of the CLI tools and Docker Compose/Helm chart configurations to ensure they follow best practices.
4. Analyzing the changes to the Janssen attribute schema in the API specification to understand the impact on access control and data visibility.

Overall, the changes appear to be routine updates and improvements, but it's important to thoroughly review them to identify any potential security implications and ensure the secure deployment and operation of the Janssen server.

Files Changed:

1. docs/janssen-server/install/docker-install/compose.md: This documentation file has been updated to replace the term "Janssen" with "Gluu flex" in the instructions for configuring the server using Docker Compose. The documentation also includes details about environment variables, a test client, and CLI tools, which should be reviewed for security implications.

2. docs/janssen-server/reference/kubernetes/helm-chart.md: This file has been updated to change the version numbers of the Janssen microservices from 0.0.0-nightly to 1.2.0. The changes to the Ingress configuration, logging and monitoring, and environment variables in the Helm chart should be reviewed to ensure a secure deployment.

3. jans-config-api/docs/jans-config-api-swagger.yaml: The changes in this file are related to the JansAttribute schema, which defines the properties of a Jans attribute. The addition of new properties and the removal of the whitePagesCanView property suggest improvements to the attribute management and access control functionality, which should be reviewed for security implications.