ZOWE user profile and ZOWE explorer

Products

• Zowe

Issue/Introduction

Multiple issues found in ZOWE explorer if both ZOWE Team configuration file (either global or project level) and Zowe user profile are in use.  

Issue 1) 

Set "authOrder": "token, bearer" in zowe.config.user.json and using APIML to connect ZOWE explorer

• Can login using "manage profile" and "log in to Authentication Service". 
• If click on the magnifying glass next to the profile to log on, it defaults to basic authentication and repeatedly asks for user credentials with the "Update credentials" option.

 

Issue 2)

Global Team Configuration file contains several Lpars.

• Lpar 1 and 2 user basic authentication -working
• Lpar 3 and 4 use APIML tokens - Working
• Lpar 5 with basic authentication with zowe.config.user.json contains different user name and IP address - not working
  • Can't log not the Lpar5 without zowe explorer adding this to the user.json. This corrupts the access to Lpar 1 and Lpar2.
     "base": {
                "properties": {},
                "secure": [
                    "user",
                    "password"
                ]
            }
  • Click "Manage Profile" and "Log out of authentication service" Zowe explorer adds this to zowe.config.user.json:
    "Lpar3": {
                "properties": {},
                "secure": [
                    "tokenValue"
                ]
            }
    Even though this property is already in zowe.config.json, and it corrupts the access to Lpar3

Environment

ZOWE explorer 3.3.1

VsCode 1.102.3

CLI Version: 8.22.0

ZOWE server v3.2.0

Resolution

Converting zowe.config.user.json into a standard zowe.config.json (either global or project team configuration file) and delete zowe.config.user.json.