---
title: The steps for Kron PAM Server (within the Secure Zone)
slug: kronpam-installation-guide/the-steps-for-kron-pam-server-within-the-secure-zone
docTags: 
createdAt: 2025-11-05T09:47:06.430Z
---

***The configurations for Kron PAM Server:***

·         All required PAM services (including **auth**) should be actively working on **10.10.0.1.**

·         On the System Configuration Man. page of the Kron PAM GUI, **mobile.tomcat.url** should be set with Kron PAM Mobile App Server’s info. (E.g., **https\://**<font color="#6366F1">**10.10.0.2**</font>**:9443/mobile-api/rest**)

·         The following jobs related to push notification system should be defined on the Kron PAM GUI: **SCPolicyNotifierJob**, **SendPushMessageJob**.

·         Using the RSA key pair created with the **aioc** alias, the environment configurations (kron-commons-config) in the Docker container on the Kron PAM server can be accessed by the Kron PAM Mobile App Server. For this, instead of using the customer's existing key pair, a self-signed certificate is used. This RSA key pair is stored in different formats and keystore files (PKCS#12 and JKS) but with the same alias (**aioc**). The jks and p12 files located at /pam/docker-mgmt/cert should be recreated with keytool commands, in this scenario. **(If the Kron PAM server and Kron PAM Mobile App Server are installed on the same server, these files should stand as is).**



*LISTING the certificates’ configurations:&#x20;*

JKS: &#x20;

```bash
sudo keytool -list -v -keystore /pam/docker-mgmt/cert/aioc.jks -storepass krondev10
```

P12:&#x20;

```bash
sudo keytool -list -v -keystore /pam/docker-mgmt/cert/aioc.p12 -storepass krondev10 -storetype PKCS12
```

*DELETING the certificates’ configurations:&#x20;*

JKS:&#x20;

```bash
sudo keytool -delete -alias aioc -keystore /pam/docker-mgmt/cert/aioc.jks -storepass krondev10
```

P12:&#x20;

```bash
sudo keytool -delete -alias aioc -keystore /pam/docker-mgmt/cert/aioc.p12 -storepass krondev10
```

*DELETING the certificate files:&#x20;*

JKS:&#x20;

```bash
rm -rf /pam/docker-mgmt/cert/aioc.jks
```

P12:&#x20;

```bash
rm -rf /pam/docker-mgmt/cert/aioc.p12
```

*CREATING the certificate files and configurations:&#x20;*

JKS:

:::BlockQuote
sudo keytool \    -genkeypair -alias aioc -keyalg RSA -keysize 2048 \    -dname "CN=localhost,OU=Kron,O=Kron,C=TR" \    -ext "SAN\:c=DNS\:localhost,DNS\:kron-commons-alfred,DNS\:kron-commons-auth,DNS\:kron-commons-license,DNS\:kron-commons-network,DNS\:kron-commons-notification,DNS\:kron-commons-config,IP:127.0.0.1,IP:**10.10.0.1**,IP:<font color="#6366F1">**10.10.0.2**</font>" \    -storepass krondev10 -keypass krondev10 -keystore /pam/docker-mgmt/cert/aioc.jks -validity 3650
:::

P12:

:::BlockQuote
sudo keytool \    -genkeypair -alias aioc -keyalg RSA -keysize 2048 \    -storetype PKCS12 -dname "CN=localhost,OU=Kron,O=Kron,C=TR" \    -ext "SAN\:c=DNS\:localhost,DNS\:kron-commons-alfred,DNS\:kron-commons-auth,DNS\:kron-commons-license,DNS\:kron-commons-network,DNS\:kron-commons-notification,DNS\:kron-commons-config,IP:127.0.0.1,IP:**10.10.0.1**,IP:<font color="#6366F1">**10.10.0.2**</font>" \    -storepass krondev10 -keypass krondev10 -keystore /pam/docker-mgmt/cert/aioc.p12 -validity 3650
:::

·         The following keytool command should be executed to import certificate:

:::BlockQuote
yes | sudo keytool \    -importkeystore -srckeystore /pam/docker-mgmt/cert/**aioc.jks** -srcstorepass **krondev10** -destkeystore /pam/docker-mgmt/cert/**aioc.p12**  -deststoretype pkcs12 -storepass **krondev10**
:::

·         The ownership and mode configurations should be changed for these files:

:::BlockQuote
sudo chown pamuser\:pam-group /pam/docker-mgmt/cert/**aioc.jks** /pam/docker-mgmt/cert/**aioc.p12**&#x20;
:::

·         Lastly, all of the docker services on the Kron PAM server should be restarted. (down & up)

:::BlockQuote
docker-compose down
:::

:::BlockQuote
docker-compose up -d
:::