Create the access token with the new access api endpoint instead of old artifactory endpoint when CLI is configured with username and password #2547
Labels
feature request
New feature or request
This is the feature request created for implementing the new access API endpoint while creating access token when the CLI is configured with username and password.
Currently, when the CLI is configured with username and password, the jf atc command will not create a token as only the access token for CLI configuration is allowed. Below is the output we get when execute jf atc command.
We can create access token with jf rt atc command but it is using the old artifactory API for creating the tokens.
Below is the sample output.
However, if we configure the CLI with an access token the jf atc command works fine and creates an access token accordingly. Below is the output.
Workaround:-
We can only use the jf atc command when CLI is configured with access-token.
What we need:-
We need to have the functionality to create access-token when the cli is configured with username and password with the new access token API endpoint.
The text was updated successfully, but these errors were encountered: