docs: clarify ZWES1601I message and explain fallback to legacy tokens#4397
docs: clarify ZWES1601I message and explain fallback to legacy tokens#4397saurabh12nxf wants to merge 3 commits intozowe:masterfrom
Conversation
Signed-off-by: Saurabh.saurabhsingh050806@gmail.com Signed-off-by: saurabh12nxf <sureshsingh09120@gmail.com>
Signed-off-by: Saurabh Singh <saurabhsingh050806@gmail.com>
|
😺 Thank you for creating this PR! Certain labels are needed to open a pull request in the
Need help? Contact the Doc Squad in the #zowe-doc Slack channel. |
The following labels are invalid: app-framework, V2 |
The following labels are invalid: area:app-framework, release:stable |
The following labels are invalid: review:, area:, Zowe, App, Framework, release:, vNext |
The following labels are invalid: review:, ,doc, area:,, Zowe,, App,, Framework, ,release:,, vNext |
The following labels are invalid: area:, Zowe, App, Framework, release:, vNext, review:, doc |
|
/labels review: doc area: cli release: V3 |
| 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. |
There was a problem hiding this comment.
Please undo this edit since it's already been addressed PR 4393
anaxceron
added
area: Zowe App Framework
ArooshLele
added
area: docs
| ### 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. |
There was a problem hiding this comment.
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:** | ||
|
|
||
| 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. |
There was a problem hiding this comment.
ZSS is not known as the "Zowe Security Server"
zowe.org and zss on github call it "Zowe System Services (ZSS)"
| **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) |
There was a problem hiding this comment.
This link does not help explain this function.
|
|
||
| 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. |
There was a problem hiding this comment.
"Legacy tokens" here means that something can log into ZSS with the non-JWT types of logins ( /login URL, basic auth, cert auth, etc)
|
@saurabh12nxf CC: @ArooshLele @anaxceron @janan07 @gauravs-20 @Gautham-coder @DivergentEuropeans |
6 participants
Describe your pull request here:
This PR adds documentation for the ZWES1601I log message under the Zowe App Framework troubleshooting section.
It improves clarity by:
Stating explicitly that the ZSS server is ready.
Explaining what "fallback to legacy tokens" means.
Providing a link to relevant configuration documentation for enabling/disabling fallback.
This helps users better understand the message and what actions (if any) they can take.
Fixes #4386
List the file(s) included in this PR:
docs/stable/troubleshoot/app-framework/zss-error-codes.md
After creating the PR, follow the instructions in the comments.