FALLAI-Denis
commented
2 years ago Hi,
Due to issue #245, I am switching between Zowe CLI V1 and Zowe CLI V2. This switchover is obtained by changing the node.js version using nvm, (node version manager, on Windows system).
In some workspaces, Git repositories, zowe.config.json files are present in the root folder.
In this case I think that Zowe Explorer, or Z Open Editor, works in Zowe CLI V2 mode, even if the installation in node.js is Zowe CLI V1: this is a priori proven because in the settings.json I declared defaultCliProfile and defaultSshCliProfile profiles which do not exist in zowe.config.json of the workspace, (nor in the home directory since I am in Zowe CLI V1), but which exist as Zowe CLI V1 profiles in the .zowe folder of the user.
In this configuration, to search for COPYBOOKs on the remote system, Z Open Editor repeatedly asks for credentials, tries to save them, and fails, with popups indicating that the profile does not exist and there are problems of cache management on profiles.
If I delete the zowe.config.json files (or rename them) in the workspace, and "reload windows" in VS Code, then everything is back to normal and the Zowe CLI V1 profiles are used.
So it seems that there is a problem detecting the version of Zowe CLI installed, when a zowe.config.json file is present in the workspace: it seems to force the use of Zowe CLI V2 , even if Zowe CLI V1 is actually installed on the workstation.
Today, we have workstations with Zowe CLI V1 and others with Zowe CLI V2, and all of them must work on the same Git repositories / Workspace in which we have declared the zowe.config.json files (for that users do not have to do it at their workstation if they are in Zowe CLI V2).
phaumer
Development environment used
Problem Description
When swithcing Workspace, (witout leaving VS Code), using different Zowe and SSH profiles, (or same named profil?), the remote user account (RACF) was revoked when searching for COPYBOOKs on the remote system.
This is the case with Zowe CLI V2, and
zowe.config.jsonfiles for a Workspace present at the root of the Workspace, and for the other Workspace absent from the Workspace (therefore using thezowe.config.jsonfile in the home directory).Zowe Explorer messages about profile cache management problem appeared. The system failed to save the new credentials and repeatedly requested them.
The case is not clearly identified and has not been reproduced, (no attempt to revoke the user account again).
In Zowe CLI V1 this problem did not occur because profile management was global at the home directory level and the same credentials were used by all Workspaces.
In Zowe CLI V2, each Workspace defines new credentials context if a
zowe.config.jsonfile is declared at the root of the Workspace, even if the profile names are identical (the credentials depend on the folder where thezowe.config.jsonfile is stored). See comment on Zowe CLI V2 - Using environment variables in profile propertiesIt turns out that the password of the remote account had been changed on the remote system, that several remote systems were accessed from Workspaces, but that all the remote systems use the same account password (RACF synchronization between the systems), and that the credentials therefore had to be updated in each Zowe CLI context.
It may be the combination, "same profile name", "Zowe CLI V2 credentials context per folder", "workspace switching", "change password on remote system" which is mishandled in Z Open Editor or in Zowe Explorer which caused the user account to be revoked on the remote system.
Observed behavior
Revoked user account by COPYBOOKs search on remote system.