Skip to Main Content
Integration


This is an IBM Automation portal for Integration 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 Submitted
Workspace StepZen
Created by Guest
Created on Nov 18, 2026

Support for secret embedding as env variable

Good afternoon team,

I’m reaching out regarding a credential-management challenge we are currently addressing with a client when configuring StepZen Graph Server (SZGS) database connections.

Context

For a client consuming an API through GraphQL, we see two main connection models:

  1. The local client maintains a local `config.yaml` containing the credentials used by GraphQL to access the database.
  2. The local client authenticates to GraphQL using client secrets or a similar mechanism, while GraphQL securely maintains the database connection details and credentials.

For a managed-service scenario, the second model is preferable because it avoids exposing database credentials and connection details to third parties.

Current limitation:

As we understand it, StepZen currently supports storing these database credentials either:

  1. In plain text in `config.yaml`.
  2. Through custom environment variables (`STEPZEN_`).

Because these values include usernames and passwords, we believe StepZen should support a secure mechanism for sourcing them from a Kubernetes Secret, or an equivalent protected credential store, rather than requiring them to be maintained in plain text.

We therefore explored the environment-variable approach. However, the `StepZenGraphServer` custom resource does not appear to support defining environment variables from a Kubernetes Secret, for example:

    env:
      - name: USR
        valueFrom:
          secretKeyRef:
            name: credentials
            key: usr
      - name: PWD
        valueFrom:
          secretKeyRef:
            name: credentials
            key: pwd

 

From our perspective, native secret integration would materially improve credential management for this client and other enterprise clients by reducing credential exposure and aligning StepZen deployments with standard Kubernetes secret-management practices.

 

Idea priority Urgent