Updating the secret when the notification (SMTP) password changes (Cognos Analytics)

Cognos® Analytics uses the notification (SMTP) password that is stored in the OpenShift® secret. Complete the following steps to update the password stored in the OpenShift secret.

Before you begin

Ensure you meet the following prerequisites:

You installed and provisioned the Cognos Analytics service on IBM Cloud Pak® for Data.
You have access to a Mac OS or Linux® computer that meets the following conditions:
- Can connect to the cluster.
- Has the oc command-line interface installed.
You can log in to the OpenShift cluster as a cluster administrator.
You know the name of the OpenShift project where the Cognos Analytics service is installed.

About this task

You need to know what you want the new notification (SMTP) password to be.

Procedure

From your local client, log in to OpenShift as a cluster administrator.

Tip: Use the Copy Login Command option in the OpenShift web console to get the oc login command.
Convert the new content store password to base64.
For example, if your new content store password is  Cognos456!, run the following command to convert the password:
```
echo -n 'Cognos456!' | base64
```
The result looks similar to the following output:
```
Q29nbm9zNDU2IQ==
```
Identify the secret object that is used for the content store.
1. Run the following command to get the secrets in the OpenShift project where Cognos Analytics is deployed:
```
oc get secrets -n OpenShift_Project | grep smtp-creds
```
2. Replace OpenShift_Project with the project where Cognos Analytics is deployed.
3. Look for a secret that looks similar to the following example:
```
ca1633358486684577-smtp-creds    Opaque                                1      151m
```
Edit the secret that you identified in the previous step.
1. Run the following command:
```
oc edit secret ca<instance-id>-smtp-creds
```
  Replace ca<instance-id>-smtp-creds with the ID of the secret from the previous step.
  
  Replace OpenShift_Project with the project where Cognos Analytics is deployed.
2. Change the following property:
```
 mailserver.properties: bWFpbHNlcn.......
```
3. The mailserver.properties property contains the following data and must be encoded as base64 when you assign it to `mailserver.properties`:
```
mailserver_host=mailserver
mailserver_port=25
mailserver_defaultsender=notifications@cognos.ibm.com
mailserver_username=
mailserver_password=
mailserver_tls_enabled=false
mailserver_rootcert_pem=
```

Run the following command to get the Cognos Analytics pod that need to be restarted:

oc get po -n OpenShift_Project | grep "ca.*ca-cpd"

Replace OpenShift_Project with the project where Cognos Analytics is deployed.

The command returns a pod similar to the following example:

ca1655142804754887-ca-cpd-cm-5cb8c4dcb5-lq7wg 1/1 Running 0 3d3h

ca1655142804754887-ca-cpd-reporting-7d7bf9dddd-mrfdb 2/2 Running 0 3d3h

ca1655142804754887-ca-cpd-rest-7cfffc7b87-j6jxz 1/1 Running 0 3d3h

ca1655142804754887-ca-cpd-smarts-c4664fdd4-ndxbq 1/1 Running 0 3d3h

Run the following command to restart the pod:
```
ooc delete po <pods id> -n OpenShift_Project
```
Replace <pods id> with the ID of the pod from the previous step.
Replace OpenShift_Project with the project where Cognos Analytics is deployed.
Wait until all of the containers are Running and the pod is in the Ready state.