Skip to Main Content
Cloud Management and AIOps


This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Planned for future release
Created by Guest
Created on Oct 18, 2024

How to set a password for the KeyStores and TrustStores when deploying IWA with Kubernetes/Helm Charts.

The password used to create the KeyStore and TrustStore is randomly generated.  Even though it can be retrieved from the env variable SSL_PASSWORD or decoding the stash (sth) file, a facility must be provided to set it to a desired password.

The following secret can be created to set the desired password to be used.  The name of the secret must take the form, <release_name>-ssl-secret, as shown below for a release name iwav1022.

apiVersion: v1
kind: Secret
metadata:
  name: iwav1022-ssl-secret
  namespace: iwa
  labels:
    app.kubernetes.io/managed-by: Helm
  annotations:
    meta.helm.sh/release-name: iwav1022
    meta.helm.sh/release-namespace: iwa
type: Opaque
data:
  SSL_PASSWORD: <encrypted password here>

 

Idea priority High