Closed adam-wolfe closed 2 months ago
Thank you for creating a bug report. We will investigate the bug and evaluate its impact on the product. If you haven't already, please ensure you have provided steps to reproduce the bug and as much context as possible.
After doing a bit more trial and error, I found that the 'zftp' profile type was not in my schema but it was in my extenders.json file. After deleting the extenders.json file, everything seems to be normal with 2.15.2. I'll assume that I caused this by jumping around between different versions of Zowe Explorer and is probably not an issue with 2.15.2. 😌
Describe the bug
After updating from 2.15.1 to 2.15.2, I run into issues if my config has a base profile that points to the APIML and has an APIML token in the secure array. Instead of using the valid APIML authentication token from my base profile, I am instead prompted for username and password any time that I use a profile that goes through the APIML (though I can hit escape to get past the username prompt and still select a filter and get a list of files).
Direct-to-service profiles continue to work normally.
To Reproduce
Expected behavior
Desktop (please complete the following information):
Additional context
Here is my config: