Create the access token with the new access api endpoint instead of old artifactory endpoint when CLI is configured with username and password
Open
Nobody has claimed this yet.
bug
- Dominant language
- Go
- Stars
- 595
- Forks
- 307
- Avg merge
- 4d 17h
- Merged PRs (30d)
- 17
Description
Describe the bug
reopen https://github.com/jfrog/jfrog-cli/issues/2547
Current behavior
see https://github.com/jfrog/jfrog-cli/issues/2547
Reproduction steps
No response
Expected behavior
No response
JFrog CLI version
https://github.com/jfrog/jfrog-cli/issues/2547
Operating system type and version
https://github.com/jfrog/jfrog-cli/issues/2547
JFrog Artifactory version
No response
JFrog Xray version
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the referenced issue #2547 and trace where the CLI creates an access token when configured with a username and password. Done means that flow uses the new access API endpoint rather than the old Artifactory endpoint, with behavior covered by the relevant existing tests if identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication, cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100