Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
npm run format
for formatting the code before submitting the pull request.This adds OIDC Authentication support allowing passwordless authentication between Azure DevOps Service and the JFrog Platform. It's the Azure DevOps equivalent of the GitHub Actions OIDC integration workflow. Essentially in JFrog an OIDC provider is configured for each Azure DevOps organization that needs to authenticate, and an identity mapping in that OIDC provider is created for each service connection that authenticates into the JFrog Platform. The Azure DevOps integration isn't quite as user friendly to configure, the details for the configuration are currently printed in the task logs but if a good how-to document was created then users could refer to that for the values.
I have tested this against a few JFrog tasks but not all of them. I'm not sure if there's a good way to add automated tests for these changes but I'm working on setting up a pipeline to run all the tasks with both OIDC and tokens to make sure it's all working and I didn't miss an async or await somewhere.
Related Issue: #494