IBM Z® Open Editor
Docs
News and Blogs
IBM Downloads
VS Code Marketplace
GitHub
Docs
News and Blogs
IBM Downloads
VS Code Marketplace
GitHub
  • Overview

    • Introduction
    • Updates and user feedback
  • Getting Started

    • Getting started with IBM Z Open Editor
    • Setting up integrations to interact with z/OS
    • Getting started with Zowe 3.0
  • Configuration

    • Setting preferences
    • Configuring your applications with ZAPP files
    • Setting property groups
    • Setting compiler options
    • Setting file associations
    • Setting language-specific tab stops and rulers
    • Enabling and disabling problems in IBM Z Open Editor
    • Enabling and disabling unreachable COBOL code warnings
    • Customizing the Outline view
    • Setting language-specific maximum line length
    • EBCDIC code pages and mappings files
    • Experimental: Formatting COBOL source code
  • Tutorials

    • Tutorial overview
    • Exploring the user interface
    • Exploring the sample files
    • COBOL editing tutorial
    • COBOL, PL/I Preprocessor tutorial
    • HLASM editing tutorial
    • REXX editing tutorial
    • Managing z/OS resources with IBM RSE API Plug-in for Zowe CLI tutorial
    • Submitting JCL to compile, link, and run jobs tutorial
  • Editing program files

    • Language References
    • Making COBOL and PL/I code changes
    • Making High Level Assembler code changes
    • Making REXX code changes
    • Making JCL code changes
    • Using and managing code snippets
    • Using the integrated Git
    • Searching for COBOL, PL/I, HLASM, and REXX components
  • Interacting with z/OS using Zowe

    • Interacting with z/OS
    • Creating a configuration profile in Zowe Explorer v3.0.0
    • Migrating your old Zowe yaml profiles for Zowe v3.0
    • Supported methods of authentication for z/OS using Zowe
    • Sharing team configuration files
    • Connecting to z/OS with Zowe Explorer walk through
    • Using the Zowe Explorer views
    • Using Zowe profiles in Z Open Editor
    • Connecting to z/OS using Zowe CLI walk through
    • Using command line to interact with z/OS
    • Interact with RSE Common Properties
  • Advanced Capabilities

    • Overview
    • Activating advanced capabilities
    • Launching a 3270 emulator from Zowe Explorer
    • z/OS Resources Table
    • Data Elements View
    • Program Control Flow Browser
    • Data Flow Browser
    • Preprocessor support
    • Custom Macros for HLASM
    • Language Detection
    • Linting with IBM ZCodeScan
    • User build with IBM Dependency Based Build (DBB)
    • Agent Mode
  • Cloud-based Editing

    • Overview to using Cloud and Browser-based platforms
    • Try Z Open Editor in the Red Hat Developer Sandbox
    • Configuring Red Hat OpenShift Dev Spaces
    • Managing Developer Workspaces
    • Managing secrets
    • Create and use custom images
    • Migrating from IBM Wazi for Dev Spaces
    • Using Z Open Editor on GitHub Codespaces
    • Using Z® Open Editor with Dev Containers
  • Troubleshooting

    • Known issues and limitations
    • Troubleshooting using log files
    • Troubleshooting for User Build
    • Uninstalling CLI plugins and VS Code extensions
  • Reference

    • IBM RSE API Plug-in for Zowe CLI commands
    • IBM RSE API Plug-in for Zowe CLI as nodejs SDK package
    • IBM RSE API Plug-in for Zowe CLI as nodejs SDK reference
    • Example Zowe configuation setups
    • IBM Z Open Editor MCP Tools
    • Accessibility and Keyboard Shortcuts
    • settings.json properties
    • Message ID Reference
    • Other Visual Studio Code extensions
  • Legal information

    • Notices
    • Trademarks
    • Privacy policy considerations

Supported methods of authentication for z/OS using Zowe

Zowe Explorer for VS Code, Zowe Explorer extenders, Zowe CLI, and Zowe CLI plugins provide various methods for users to authenticate and secure credentials. Secure credential encryption is included in Zowe CLI SDKs, storing credentials and other values set by the user to be stored securely using the local device's credential manager or external secret vaults, and provided as environment variables.

Types of authentication supported by Zowe include passwords, passphrases, JSON web token (JWT) authentication, single sign-on (SSO), and multi-factor authentication (MFA). Zowe with z/OSMF connection requires authenticating with the Zowe API Mediation Layer (ML) for SSO, JWT, and MFA support.

RSE connections with Zowe Explorer and RSE CLI plug-in supports passwords, passphrases, and JWT authentication directly with the RSE API host component. If the RSE API host component is registered with the Zowe API ML, all of the methods of authentication supported by the API ML will be available for RSE profiles as well.

Single sign-on support

After an RSE profile is created and is accessible in Zowe Explorer, users can use single sign-on (SSO) for connecting to the RSE API host component in Zowe Explorer 1.22.0 and later versions. JWTs are stored securely in the profile's file. For RSE profiles connecting directly to the RSE API, follow the steps below:

Logging in to authentication service

Zowe Explorer UI

  1. Right-click the profile name in the Zowe Explorer tree view and click Login to Authentication Service.
  2. Enter credentials for z/OS connection when prompted.

When the login is successful, you will receive the message Login to authentication service was successful. from Zowe Explorer.

Zowe CLI

  1. In the terminal, enter the command zowe rse auth login.
  2. Enter credentials for z/OS connection when prompted.

When the login is successful, you will receive a message with information about the JWT, including the expiration date and time as well as the creation date and time of it.

Logging out of authentication service

Zowe Explorer UI

Right-click on the profile name in the Zowe Explorer tree view and select Logout from Authentication Service.

When the logoff is successful, you will receive the message Logout from authentication service was successful. from Zowe Explorer.

Zowe CLI

In the terminal, enter the command zowe rse auth logout.

When the logoff is successful, you will receive the message JWT Token has been retired..

If you are obtaining authentication tokens from the API Mediation Layer, see Connecting profiles to API Mediation Layer.

For an example of the team configuration file with RSE profile authenticating with API Mediation Layer, see Single sign-on support for IBM RSE CLI plugin.

Multi-factor authentication

You can use multi-factor authentication (MFA) with Zowe team configuration profiles. Zowe Explorer and Zowe CLI support multi-factor authentication. The client setup and use of MFA vary depending on your site configuration, see setup integration for MFA for details on different client setup scenarios.

Using environment variables for authentication in Zowe Explorer

To support development environments such as OpenShift Red Hat Dev Spaces, GitHub Codespaces, or any development environment where credentials are managed in external or Cloud-based credential vaults, you can set user credentials through environment variables to be referenced in Zowe team configuration profiles.

  1. See

    • Managing secrets in the Dev Spaces section on how to create such environment variables in OpenShift Dev Spaces,
    • Connect to a z/OS® system using a VPN in the Codespaces section on how to create such environment variables in GitHub Codespaces, or
    • Check with your system administrator on how to securely initialize environment variables on your system, if you are using another technology with an external credentials vault.
  2. Configure your Zowe team configuration profiles to use the environment variables as values for the user and password properties, as shown below.

    {
      "profiles": {
        "rse1": {
          "type": "rse",
          "properties": {
            "port": 443,
            "host": "example.host",
            "user": "$ZOWE_OPT_USER",
            "password": "$ZOWE_OPT_PASSWORD"
          }
        }
      }
    }
    

After you configure it, you are automatically logged on using the credentials provided by the environment variables when you start interacting with your Zowe connection profiles, for example by running a search query for data sets in Zowe Explorer.

Last Updated: 1/21/26, 4:24 PM
Contributors: KRISTINA MAYO, Chun Hong Zheng, Nimma Likhitha, likhithanimma1, phaumer, Esther M, Billie Simmons
Prev
Migrating your old Zowe yaml profiles for Zowe v3.0
Next
Sharing team configuration files