From 4c1b97eff9d7d93af7822feb4b819e2f9c7bf164 Mon Sep 17 00:00:00 2001 From: saurabh12nxf Date: Wed, 7 May 2025 13:36:18 +0530 Subject: [PATCH 1/2] Clarified documentation for team configuration in Zowe CLI and Explorer Signed-off-by: Saurabh.saurabhsingh050806@gmail.com Signed-off-by: saurabh12nxf --- docs/appendix/zowe-glossary.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/appendix/zowe-glossary.md b/docs/appendix/zowe-glossary.md index 72a5807109..b79fceefb7 100644 --- a/docs/appendix/zowe-glossary.md +++ b/docs/appendix/zowe-glossary.md @@ -120,8 +120,7 @@ Services are deployed using one or more service instances, which share the same #### Team configuration A method of storing and managing Zowe CLI and Zowe Explorer *team* and *user* profiles introduced in Zowe Version 2. - -This method saves team-specific profiles in the `zowe.config.json` configuration file and user-specific profiles in the `zowe.config.user.json` configuration file. The location of the configuration file determines whether these profiles are applied *globally* or *per project*. +This method saves team-specific profiles in the *zowe.config.json* configuration file and user-specific profiles in the *zowe.config.user.json* configuration file. These profiles are stored locally on the user's client system (e.g., in Visual Studio Code) and determine whether they are applied *globally* (to all projects) or *per project*. This configuration is for managing Zowe CLI and Explorer settings on the local client and does not store or affect z/OS configurations. #### Web Explorers From 72b17b786f545d0a4c67776dfb65ae676b49170c Mon Sep 17 00:00:00 2001 From: Saurabh Singh Date: Wed, 7 May 2025 19:30:31 +0530 Subject: [PATCH 2/2] docs: clarify ZWES1601I message and explain legacy token fallback Signed-off-by: Saurabh Singh --- .../app-framework/zss-error-codes.md | 24 +++++++++++++++---- 1 file changed, 19 insertions(+), 5 deletions(-) diff --git a/docs/troubleshoot/app-framework/zss-error-codes.md b/docs/troubleshoot/app-framework/zss-error-codes.md index df39181f27..7cf62398de 100644 --- a/docs/troubleshoot/app-framework/zss-error-codes.md +++ b/docs/troubleshoot/app-framework/zss-error-codes.md @@ -193,15 +193,29 @@ The following error message codes may appear on ZSS log. Use the following messa ### ZWES1601I - Server is ready to accept JWT `with`(or `without`) fallback to legacy tokens +ZSS server is ready to accept JWT with (or without) fallback to legacy tokens. - **Reason:** +**Reason:** - Server is ready to accept JWT `with` or `without` fallback to legacy tokens. +This message indicates that the ZSS (Zowe Security Server) has successfully started and is ready to accept JWT (JSON Web Token)-based authentication. Depending on your configuration, it may also accept legacy Zowe tokens as a fallback. - **Action:** +**What does "with (or without) fallback to legacy tokens" mean?** + +ZSS can support two types of authentication tokens: +- **JWT (JSON Web Tokens)** – the default and more secure method. +- **Legacy tokens** – used in older versions of Zowe. + +If fallback is enabled, users with legacy tokens can still authenticate. If fallback is disabled, only JWT tokens are accepted. + +**How to Configure Fallback:** + +You can enable or disable fallback in your `zowe.yaml` configuration file. +Refer to: [Zowe Authentication Configuration](https://docs.zowe.org/stable/user-guide/configure-zowe-runtime/#authentication-configuration) + +**Action:** + +No action required unless you want to modify the authentication method. - No action required. ## ZSS error messages