-
Notifications
You must be signed in to change notification settings - Fork 92
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.
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
Log out from API ML is not available anymore with Manage Profile menu #2633
Log out from API ML is not available anymore with Manage Profile menu #2633
Comments
Thank you for creating a bug report. |
This was resolved with PR #2639 and will be included in an upcoming release Screen.Recording.2024-01-05.at.4.56.19.PM.mov |
I ran into something very similar this morning even with a new build of the main branch. #2652 I found that I had a zowe.config.json in my user home directory as well as in the ~/.zowe directory. After deleting the config in my user home directory, I have been unable to recreate this issue, and I do not know what caused the behavior to start initially. So, I think this will not be resolved by #2639. |
After some more trial and error, I have been able to recreate this. It may be related to #2637. Here is my config:
If you delete the secure array from the 'zosmf' profile, the Manage Profiles menu for 'zosmf-apiml' returns to normal. |
Hello, seems I have this issue appeared again.
This time I use
{
"$schema": "./zowe.schema.json",
"profiles": {
"mfts": {
"properties": {
"ccid": "TEST",
"comment": "Changes by ME"
},
"profiles": {
"demobox": {
"type": "endevor-location",
"properties": {
"subsystem": "DEMOBOX"
},
"secure": []
},
"my-sandbox": {
"type": "endevor-location",
"properties": {
"subsystem": "MYBOX"
},
"secure": []
}
}
},
"mfne": {
"properties": {
"instance": "MFNE",
"type": "*",
"ccid": "TEST",
"comment": "Changes by ME"
},
"profiles": {
"other-sandbox": {
"type": "endevor-location",
"properties": {
"environment": "DEV",
"stageNumber": "1",
"system": "SYSTEST",
"subsystem": "SBSTEST"
},
"secure": []
}
}
}
},
"defaults": {
"endevor-location": "mfts.my-sandbox"
}
}
{
"$schema": "./zowe.schema.json",
"profiles": {
"base": {
"type": "base",
"properties": {
"host": "apiml.services.net",
"protocol": "https",
"port": 60608,
"rejectUnauthorized": true,
"tokenType": "apimlAuthenticationToken"
},
"secure": ["tokenValue"]
},
"my-mf": {
"profiles": {
"zosmf": {
"type": "zosmf",
"properties": {
"port": 1443
},
"secure": []
},
"zosmf-apiml": {
"type": "zosmf",
"properties": {
"basePath": "/ibmzosmf/api/v1"
}
},
"endevor-apiml": {
"type": "endevor",
"properties": {
"basePath": "/caendevorapi/api/v2"
}
}
}
},
"mfts": {
"properties": {
"environment": "DEV",
"instance": "MFTS",
"system": "SYSPROD",
"stageNumber": "1",
"type": "*"
},
"profiles": {
"app-hotfixes": {
"type": "endevor-location",
"properties": {
"environment": "QA",
"subsystem": "SYSPROD"
},
"secure": []
},
}
},
},
"defaults": {
"base": "base",
"endevor": "my-mf.endevor-apiml",
"endevor-location": "mfts.app-hotfixes",
"zosmf": "my-mf.zosmf-apiml"
},
"autoStore": true
} After the API ML successful login using "Manage profile" menu on Can confirm though if I remove the User config everything works as expected and the logout option is in place. |
@roman-kupriyanov Thanks for reporting this! We have found the underlying issue lies in Imperative. I've opened zowe/zowe-cli#2135 to fix it there. Once it is merged we'll update the Imperative dependency in Zowe Explorer 🙂 |
Describe the bug
After using the "Manage Profile -> Log in to authentication service" option for the z/OSMF type of the profile and successful login, the "Log out" option does not appear anymore after the introduction of "Manage Profile" menu.
To Reproduce
Expected behavior
After successful login to API ML using Zowe Explorer, it is expected to be able to logout using ZE too. For now the only way is to use Zowe CLI for that.
Screenshots
Desktop:
Additional info
Base profile in the Team config:
Actual z/OSMF profile:
The text was updated successfully, but these errors were encountered: