Skip to content
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

Search operation does not prompt for login for APIML profile #2259

Closed
Tracked by #2252
t1m0thyj opened this issue Apr 27, 2023 · 4 comments · Fixed by #3111
Closed
Tracked by #2252

Search operation does not prompt for login for APIML profile #2259

t1m0thyj opened this issue Apr 27, 2023 · 4 comments · Fixed by #3111
Assignees
Labels
enhancement New feature or request priority-medium Not functioning - next quarter if capacity permits
Milestone

Comments

@t1m0thyj
Copy link
Member

Steps to Reproduce

  1. Create a team config file with zowe config auto-init that contains a z/OSMF profile through APIML. Add a second z/OSMF profile to the config that connects direct to service. See Config with both APIML and direct-connection profiles gets authentication errors zowe-cli#1868 for an example of such a config.
  2. Delete the Zowe/secure_config_props secret from your OS vault so that there are no secure properties stored.
  3. Launch Zowe Explorer in the same project directory as the team config file, and click the 🔍 icon in the Data Sets tree for the APIML profile.
    image

Actual Behavior
Two error messages are shown, neither of which tell me how to correct the situation.
image

Expected Behavior
When I click the 🔍 icon for the direct-to-service profile, I am prompted to enter username and password.
I would expect the APIML profile to behave similarly and prompt me for credentials to log in to APIML and obtain a token.

@t1m0thyj t1m0thyj added the enhancement New feature or request label Apr 27, 2023
@github-actions
Copy link

Thank you for raising this issue.
The community has 90 days to upvote 👍 the issue.
If it receives 10 upvotes, we will move it to our backlog. If not, we will close it.

@t1m0thyj t1m0thyj added the priority-medium Not functioning - next quarter if capacity permits label Apr 28, 2023
@JillieBeanSim JillieBeanSim mentioned this issue Jul 7, 2023
29 tasks
@JillieBeanSim JillieBeanSim mentioned this issue Sep 25, 2023
31 tasks
@t1m0thyj t1m0thyj added this to the v3.0.0 GA milestone Jul 22, 2024
@t1m0thyj t1m0thyj self-assigned this Sep 13, 2024
@t1m0thyj t1m0thyj linked a pull request Sep 13, 2024 that will close this issue
15 tasks
@JillieBeanSim
Copy link
Contributor

JillieBeanSim commented Sep 19, 2024

Hey @t1m0thyj I see you are working on a draft PR tied to this, also the title & description makes it sound like a bug.
Questions?

  1. should this be a bug instead of enhancement?
  2. are we planning for it to be included in GA or later?

@t1m0thyj
Copy link
Member Author

@JillieBeanSim A bug probably makes sense, and I'm hoping to get a fix included in GA with the draft PR 😋

@JillieBeanSim
Copy link
Contributor

Thanks @t1m0thyj I will leave it in the milestone for the GA

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request priority-medium Not functioning - next quarter if capacity permits
Projects
Status: Closed
Development

Successfully merging a pull request may close this issue.

2 participants