jfrog / jfrog/jfrog-cli-security

jf docker scan does not support command option auth

Open
#53 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature request
Dominant language
Go
Stars
13
Forks
50
Avg merge
3d 48m
Merged PRs (30d)
26

Description

Describe the bug

The current docs suggest that command options can be used to configure the url and auth options for the xray server when scanning. https://docs.jfrog-applications.jfrog.io/jfrog-applications/jfrog-cli/cli-for-jfrog-security/authentication
https://docs.jfrog-applications.jfrog.io/jfrog-applications/jfrog-cli/cli-for-jfrog-security

These options work when running jf audit, but not jf docker scan, although the structure of the documentation seems to suggest it should work for both.

Current behavior

Output:

JFrog Xray URL must be provided in order run this command. Use the 'jf c add' command to set the Xray server details.

Reproduction steps

Command:

jf docker scan --url {my-server-url} --user {my-user} --password {my-password} {my-local-image}

Expected behavior

The jf docker scan command uses the provided url and credentials to run the scan; or, the documentation reflects that it only works when running the audit command.

JFrog CLI-Security version

1.0.5

JFrog CLI version (if applicable)

2.55.0

Operating system type and version

Version used by releases-docker.jfrog.io/jfrog/jfrog-cli-full-v2-jf:2.55.0

JFrog Xray version

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the implementation and option handling for the jf docker scan command, then reproduce the issue with the documented --url, --user, and --password command. Done means the scan uses those values like jf audit, or the authentication documentation clearly states that they apply only to audit.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.