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

[BUG] User with developer role should be able to review scans. #229

Closed
awoodobvio opened this issue Feb 15, 2022 · 2 comments · Fixed by #243
Closed

[BUG] User with developer role should be able to review scans. #229

awoodobvio opened this issue Feb 15, 2022 · 2 comments · Fixed by #243

Comments

@awoodobvio
Copy link

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

  1. Use credentials that have "Developer" access to the IQ organization/application in question
  2. Attempt to use the extension
  3. You will get a 403 error. It appears that the extension requires scan permissions

Expected behavior
Developers should be able to "browse" the scan results from the CI system without having direct access to create a new scan or disrupt the current scans that are produced by the CI system.

Desktop (please complete the following information):

  • OS: Windows
  • NodeJS Version: 12.22.7
  • VS Code Version: 1.64.2
  • Version of Extension 1.2.3

Additional context
Add any other context about the problem here.

cc @bhamail / @DarthHater

@awoodobvio awoodobvio added the bug Something isn't working label Feb 15, 2022
@awoodobvio awoodobvio changed the title [BUG] [BUG] User with developer role should be able to review scans. Feb 16, 2022
@madpah
Copy link
Collaborator

madpah commented Feb 23, 2023

Hi @awoodobvio - thanks for raising this.

You are indeed correct that Scan permissions are required, as the VSCode Extension does perform a scan against Nexus Lifecycle each time dependencies change or you request a refresh. There is no way around this - scan permissions are required.

We will however note that documentation should be updated for this plugin.

@brent-spiner
Copy link

🎉 This issue has been resolved in version 1.3.2 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants