Where is default environment properties saved?

[kukuhprastyono]

i run the Klaw use Docker Compose, i can't find application.properties inside the docker container, where is the location of default environment properties?
can i define this properties locally and how?

[aindriu-aiven]

Hey @kukuhprastyono thanks for asking!

The docker image is built with the default application.properties file the one found in resource/main/application.properties in both core and cluster-api.

We have a couple of options to override that configuration, we do have some documentation on how to configure the docker images here

However I am a heavy user of docker myself and I like to use an external application.properties.

To do this i update the docker compose with an additional environment variable see
SPRING_CONFIG_LOCATION: "/klaw/klaw-application.properties"

Within this klaw-application.properties I define all the details from SSO and SSL to my database connection string.

Similarly I do the same for the cluster-api by setting SPRING_CONFIG_LOCATION: "/klaw/cluster-application.properties"

---
services:
  klaw-core:
    image: klaw-core:latest
    container_name: klaw-core
    environment:
      KLAW_UIAPI_SERVERS: "http://klaw-core:9097"
      KLAW_CLUSTERAPI_URL: "http://klaw-cluster-api:9343"
      SPRING_CONFIG_LOCATION: "/klaw/klaw-application.properties"
    volumes:
      - "klaw_data:/klaw"
    extra_hosts:
      - "moby:127.0.0.1"
    ports:
      - 9097:9097
  klaw-cluster-api:
    image: klaw-cluster-api:latest
    container_name: klaw-cluster-api
    environment:
      KLAW_CLUSTERAPI_ACCESS_BASE64_SECRET: dGhpcyBpcyBhIHNlY3JldCB0byBhY2Nlc3MgY2x1c3RlcmFwaQ==
      SPRING_CONFIG_LOCATION: "/klaw/cluster-application.properties"
    volumes:
      - "klaw_data:/klaw"
    extra_hosts:
      - "moby:127.0.0.1"
    ports:
      - 9343:9343
volumes:
  klaw_data:
    driver: local

If you prefer you can simply override all the application.properties settings as environment variables but when there are lots of changes I think it is easier to read the external application.properties.

Example settings overriding the SSL settings

environment:
    KLAW_CLUSTERAPI_ACCESS_BASE64_SECRET: dGhpcyBpcyBhIHNlY3JldCB0byBhY2Nlc3MgY2x1c3RlcmFwaQ==
    SPRING_DATASOURCE_URL: "jdbc:h2:file:/klaw/klawprodb;DB_CLOSE_ON_EXIT=FALSE;DB_CLOSE_DELAY=-1;MODE=MySQL;    CASE_INSENSITIVE_IDENTIFIERS=TRUE;"
    SERVER_SSL_KEYSTORE: "/klaw/client.keystore.p12"
    SERVER_SSL_TRUSTSTORE: "/klaw/client.truststore.jks"
    SERVER_SSL_KEYSTOREPASSWORD: "klaw1234"
    SERVER_SSL_KEYPASSWORD: "klaw1234"
    SERVER_SSL_TRUSTSTOREPASSWORD: "klaw1234"
    SERVER_SSL_KEYSTORETYPE: "pkcs12"

Other things to note are that their may be slight differences in the docker compose for linux and for mac/windows they can be found on the same page as earlier starting with the linux file

Also if you are trying to find the location of the /klaw/ mount when klaw-core and cluster-api are running you can run the following command to get the location of it.
docker inspect -f '{{ .Mounts }}' klaw-cluster-ap

Please let me know if that answers your question!

Thanks,
Aindriú

[aindriu-aiven]

@kukuhprastyono

Thanks for reaching out again.

Just to clarify are you trying to set the value for dev_cluster4.kafkassl.key.pwd or retrieve the value?
Also are you using an external application.properties file or are you using environment variables in the docker-compose.yaml to set the properties?

here is an example of how I would set the connection details in the external properties file.

dev_cluster4.kafkassl.keystore.location=/klaw/klaw-kafka-client.keystore.p12
dev_cluster4.kafkassl.keystore.pwd=password
dev_cluster4.kafkassl.key.pwd=password
dev_cluster4.kafkassl.keystore.type=pkcs12
dev_cluster4.kafkassl.truststore.location=/klaw/klaw-kafka-client.truststore.jks
dev_cluster4.kafkassl.truststore.pwd=password
dev_cluster4.kafkassl.truststore.type=jks

I set the client keystore and truststore using the directions on the "Quick Connect" Quide on the Aiven Kafka Service overview page.
Here is step 3 specifically for the keystore and truststore. I then copy those to the /klaw/ volume discussed in my previous answer.

3. Create keystore and truststore:
3.1 Use the openssl utility to create the keystore with the service.key and service.cert files downloaded previously:
$

openssl pkcs12 -export -inkey service.key -in service.cert -out client.keystore.p12 -name service_key


Enter a password to protect the keystore and the key, when prompted.
3.2 In the folder where the certificates are stored, use the keytool utility to create the truststore with the ca.pem file as input:
$

keytool -import -file ca.pem -alias CA -keystore client.truststore.jks


Enter a password to protect the truststores and reply yes to confirm trusting the CA certificate, when promted.
The result are the keystore named client.keystore.p12 and truststore named client.truststore.jks that can be used for client applications configuration in the next steps.

Please let me know if this helped!

[kukuhprastyono]

yes, i am trying to set the value dev_cluster4.kafkassl.key.pwd but i don't know the value,
yes, i am use application.properties file and save the keystore and truststore in same directory with application.properties

[aindriu-aiven]

I just did a quick test there as I wasn't 100% sure.

But the value for dev_cluster4.kafkassl.key.pwd should be the same as dev_cluster4.kafkassl.keystore.pwd in my own setup for connecting to kafka.

[muralibasani]

@kukuhprastyono regarding key password value : When a keystore is created, it would prompt for key pwd, keystore pwd. So it depends on how you got them created. Please check.

And regarding listTopics time out error, probably it could not establish a connection, hence timeout. Please try to fix the above ssl connectivity issue, and this could be resolved on its own.

[kukuhprastyono]

Thank you @aindriu-aiven @muralibasani for your answer, my timeout error caused by klaw and kafka cluster run in different private network