Securing Enterprise Mainframe Credentials in CI/CD Runners using Zowe Secure Credential Store
Executive Summary: Securing Enterprise Mainframe Credentials in CI/CD Runners using Zowe Secure Credential Store
Never commit plaintext mainframe passwords to configuration files. Discover how to install and configure the Zowe Secure Credential Store plugin, integrate with OS keychains, and pass temporary secrets securely in automated GitHub Actions runners.
1 Problem Statement & Architecture Context: Securing Enterprise Mainframe Credentials in CI/CD Runners using Zowe Secure Credential Store
Developers and automation scripts accidentally commit zowe.config.json containing unencrypted mainframe passwords to Git repositories, triggering security audits and credential revocations.
2 Technical Root Cause & Architecture Mechanics
By default, Zowe CLI v2 stores non-secure properties in zowe.config.json and sensitive fields (passwords, private keys, client secrets) in the operating system's native secure credential vault via the @zowe/secure-credential-store-for-zowe-cli plugin.
If the plugin is missing or in headless Linux container environments without a graphical keychain (like GitHub Actions runners), credential lookups fail.
3 Implementation Guide & Modernization Strategy
# 1. Install Secure Credential Store Plugin
zowe plugins install @zowe/secure-credential-store-for-zowe-cli
# 2. Secure Storage on Desktop (Windows / macOS)
When you run zowe auth login, Zowe stores passwords in:
- Windows: Windows Credential Manager
- macOS: Apple Keychain
- Linux Desktop: Secret Service / KWallet
# 3. Headless CI/CD Runners (GitHub Actions / Docker)
In headless Linux environments where no desktop keychain daemon exists, pass credentials dynamically via environment variables without modifying files:
- name: Run Zowe Command in GitHub Actions
env:
ZOWE_OPT_HOST: ${{ secrets.ZOS_HOST }}
ZOWE_OPT_USER: ${{ secrets.ZOS_USER }}
ZOWE_OPT_PASSWORD: ${{ secrets.ZOS_PASSWORD }}
run: |
zowe zos-jobs list jobs --owner "$ZOWE_OPT_USER"
Technical Specifications Matrix
| Attribute | Specification |
|---|---|
| Target Environment | IBM z/OS • DevOps & Automation |
| Key Technologies | Zowe CLI, Security, Credentials |
| Delivery SLA | Accelerated Sprint Delivery via StackMF Pods |
| Technical Reviewer | Anshu, Chief Technology Architect • StackMF Architecture Pod |
Production Readiness & Verification Checklist
- Add `zowe.config.user.json` to `.gitignore` to prevent private local overrides from being committed.
- Use automated pre-commit hooks (`git-secrets` or `trufflehog`) to block commits containing mainframe passwords.
- Rotate service account passwords every 90 days and manage via enterprise secrets managers.
? Frequently Asked Questions
What is the root cause of Securing Enterprise Mainframe Credentials in CI/CD Runners using Zowe Secure Credential Store? ↓
How do you resolve Securing Enterprise Mainframe Credentials in CI/CD Runners using Zowe Secure Credential Store in production? ↓
How can teams prevent Securing Enterprise Mainframe Credentials in CI/CD Runners using Zowe Secure Credential Store in enterprise pipelines? ↓
Recommended Technical Runbooks
Migrating from Broadcom Endevor to Git & Modern CI/CD using Zowe CLI and IBM DBB
Broadcom CA-7 / CA-11 Decoupling: Migrating 20,000+ JCL Batch Schedules to Stonebranch or Control-M
Building Enterprise REXX Automation: Scripting TSO/E, ISPF Panels, and SDSF Job Parsing
Authoritative Reference Documentation
Official IBM manuals, Redbooks, and vendor technical advisories:
This diagnostic runbook is published by StackMF Technologies LLP for educational and architectural reference only. All code snippets, JCL, and procedures are provided "AS IS" without warranty of any kind. Always test changes thoroughly in non-production sysplex environments prior to production rollout.
IBM, z/OS, CICS, Db2, IMS, RACF, and IDz are registered trademarks of International Business Machines Corporation. Broadcom, CA-7, and Endevor are trademarks of Broadcom Inc. All other trademarks belong to their respective owners and are referenced under the Nominative Fair Use Doctrine (US Lanham Act 15 U.S.C. ยง 1125 / Section 30 of the Indian Trade Marks Act, 1999) solely for technology compatibility and diagnostic identification. StackMF Technologies LLP is an independent consulting entity not affiliated with or endorsed by these vendors. View Full Legal & IP Policy →
Struggling with Critical Mainframe Incidents or Vendor Renewal Pressure?
StackMF deploys certified Senior Mainframe Engineers fluent in both z/OS legacy internals (COBOL, DB2, CICS, VSAM, CA-7, Endevor) and modern cloud stacks (React, Kafka, AWS, Git). Onboard dedicated pods in 48 hours or cut Broadcom licensing by 60%.