Renew expired UMB certificates

How to renew the certificates used to authenticate against shared services, such as UMB.


There are 2 service accounts used to access UMB:

  1. cki-amqp-bridge: Read only permission.

  2. cki-umb-messenger: Write permission on the following topics:

    • VirtualTopic.eng.cki.ready_for_test

These service accounts use certificates to authenticate, which need to be renewed every 1 year.

  1. Accessing Shared Services

  2. UMB Getting Started

  3. How to: Request UMB Certificates

  4. INC1643166: Service Account creation ticket.

  5. RITM0854859: UMB authorization ticket.


The instructions can be found on the Step 3 of Accessing Shared Services.

  1. Locally checkout the IT-IAM Utilities repository.

  2. Using the PKI/ script, generate the certificates for all the accounts. The script will ask for the service accounts password, get it from the credentials repository.

    Note: It’s important to execute the script from inside the PKI folder otherwise it won’t work 🤦

    Note2: Non production service accounts are different service accounts, but the script automatically prepends nonprod- to the name when using the nonprod option, so you’ll need to remove it from the cmd call.

    Note3: It is recommended to run the command inside a container as the script needs some dependencies.

    Note4: The generated certificates are left in /tmp, so mount it as a volume to access them from outside of the container easily.

    $ git clone
    $ podman run --rm -it -v $PWD/utility:/utility $PWD/output:/tmp
    (container) $ dnf install -y certmonger openldap-clients openssl java-11-openjdk
    (container) $ cd /utility/PKI
    (container) /utility/PKI $ ./ cki-amqp-bridge prod
    (container) /utility/PKI $ ./ cki-amqp-bridge nonprod
    (container) /utility/PKI $ ./ cki-umb-messenger prod
    (container) /utility/PKI $ ./ cki-umb-messenger nonprod
  3. Update the certificates on the credentials repository overwriting the existing files in the certs/ path.

    mv $PWD/output/{cki-amqp-bridge.*,nonprod-cki-amqp-bridge.*,cki-umb-messenger-*,nonprod-cki-umb-messenger-*} ${CREDENTIALS_REPO}/certs
  4. Generate the pem file by concatenating the crt and key files, for each of the accounts.

    cat ${SA_NAME}.crt ${SA_NAME}.key > ${SA_NAME}.pem
  5. Add the contents of the pem files to the secrets.yml file.

    credentials/ $ export CKI_AMQP_BRIDGE_DEV_PEM=$(cat certs/nonprod-cki-amqp-bridge.pem | base64 -i -w 64 | tr -d '\n')
    credentials/ $ export CKI_AMQP_BRIDGE_PROD_PEM=$(cat certs/cki-amqp-bridge.pem | base64 -i -w 64 | tr -d '\n')
    credentials/ $ export CKI_UMB_MESSENGER_DEV_PEM=$(cat certs/nonprod-cki-umb-messenger.pem | base64 -i -w 64 | tr -d '\n')
    credentials/ $ export CKI_UMB_MESSENGER_PROD_PEM=$(cat certs/cki-umb-messenger.pem | base64 -i -w 64 | tr -d '\n')
    deployment-all/ $ ./ secrets.yml
    Appending to secrets.yml...
    Variable name: CKI_AMQP_BRIDGE_DEV_PEM
    Secret value (not echoed, empty takes from env): [ENTER]
    Variable name: CKI_AMQP_BRIDGE_PROD_PEM
    Secret value (not echoed, empty takes from env): [ENTER]
    Variable name: CKI_UMB_MESSENGER_DEV_PEM
    Secret value (not echoed, empty takes from env): [ENTER]
    Secret value (not echoed, empty takes from env): [ENTER]
Last modified June 14, 2021: Adjust topics for umb-messenger UMB service account (f98b8ec)