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.

Add a new idea Subscribe
Status Submitted
Workspace IBM Turbonomic ARM
Categories Authentication & Security
Created by Guest
Created on Feb 17, 2026

RELATED IDEAS

Make it possible to read the openIdClientSecret from a K8s secret instead of hardcoded in the xl-release.

Hi,

When connecting Turbonomic to e.g. Okta with OIDC the settings look like this:

apiVersion: charts.helm.k8s.io/v1alpha1
kind: Xl
metadata:
 name: xl-release
spec:
 properties:
   api:
     openIdEnabled: true
     openIdClients: okta
     openIdClientId: xxxxxxxxxh1xhQnSKxxxx
     openIdClientSecret: xxxxxxxxxxtIhVCIRUnhq4xxxxxxxDdhLdqx0 <---- plaintext is not good
     openIdAccessTokenUri: https://vmturbo.okta.com/oauth2/v1/token
     openIdUserAuthorizationUri: https://vmturbo.okta.com/oauth2/v1/authorize
     openIdUserInfoUri: https://vmturbo.okta.com/oauth2/v1/userinfo
     openIdJwkSetUri: https://vmturbo.okta.com/oauth2/v1/keys
 

The  openIdClientSecret is in plaintext in the settings file. We use GitOps/ArgoCD for deploying and we don't want to commit the secret in Git. It would be great if this could be created as a K8s Secret and then referenced in the settings, i.e. spec.properties.api.openIdClientKubernetesSecret: <the secret name> or something like that. The same way the external DB username/password can be referenced in a secret.

/f

 

Idea priority Low

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.