-
Notifications
You must be signed in to change notification settings - Fork 65
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
Unable to use Reference Token with Azure DevOps Service Connection even though the connection Validates using a Reference Token #509
Comments
Never mind. So, when I created the user account for build server integration, I also created an access token, both a JWT and a Reference token. The help bubble for the Reference Token says that it can be used anywhere as a password, API Key, or, and this is the important one, a Bearer token. That, apparently, is not true, at least, not for Nuget. Here's more of the log from a failing build:
So, I cannot use the reference token as a bearer token, I have to use the full JWT token. But here's the thing, I validated the ServiceConnection in Azure DevOps with the Reference token and it validated just fine—the connection to the API could be established. This seems like a bug to me—perhaps in Azure DevOps Server. So, I'm going to change the title of this issue and let someone else decide whether this is not a Jfrog problem. (It's possible it's a littel of both.) |
Describe the bug
Important
Please see my comment below. I'm leaving the original issue as stated for broader context purposes, but the issue is not what it at first seemed. What follows below is the original issue, but please see my comment for the real issue at hand.
I have an Azure DevOps Server ServiceConnection to Artifactory which is using token-based authentication for the connection.
However, when using the
JfrogDotNetCore@1
task in an Azure DevOps YAML pipeline with the following configuration:running the build results in the following error output:
If I'm using a ServiceConnection, then I should not need to provide a
username
input to the task.Current behavior
If you don't specify a
username
input to theJfrogDotNetCore@1
task in a YAML pipeline even though you are using a ServiceConnection, the task ends in an error.Reproduction steps
Run a build pipeline with a valid task configured as shown below:
When using a ServiceConnection with token-based authentication, a username should not be required. (The Classic build pipeline editor does not prompt for a Username whin using a ServiceConnection.)
Expected behavior
The task does not require a
username
input when using a ServiceConnection.Azure DevOps extension name and version
2.92 I think.....
JFrog CLI version
2.53.1
Operating system type and version
Windows Server 2019
JFrog Artifactory version (if relevant)
No response
JFrog Xray version (if relevant)
No response
JFrog Distribution version (if relevant)
No response
The text was updated successfully, but these errors were encountered: