Skip to content

docs: clarify ZWES1601I message and explain fallback to legacy tokens #4397

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

docs: clarify ZWES1601I message and explain fallback to legacy tokens #4397

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
4c1b97e
Clarified documentation for team configuration in Zowe CLI and Explorer
saurabh12nxf May 7, 2025
72b17b7
docs: clarify ZWES1601I message and explain legacy token fallback
Aura129 May 7, 2025
1de2f2e
Merge branch 'master' into fix-zwes1601i-message
anaxceron May 8, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 1 addition & 2 deletions docs/appendix/zowe-glossary.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please undo this edit since it's already been addressed PR 4393


#### Web Explorers

Expand Down
24 changes: 19 additions & 5 deletions docs/troubleshoot/app-framework/zss-error-codes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You cannot made edits to this line.
This is the line the log prints out. If you edit it, it would be incorrect.

ZWES1601I Server is ready to accept JWT with 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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ZSS is not known as the "Zowe Security Server"
zowe.org and zss on github call it "Zowe System Services (ZSS)"


**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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Legacy tokens" here means that something can log into ZSS with the non-JWT types of logins ( /login URL, basic auth, cert auth, etc)


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)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This link does not help explain this function.


**Action:**

No action required unless you want to modify the authentication method.

No action required.

## ZSS error messages

Expand Down
Loading