Skip to content

Conversation

@HenrikStanley
Copy link

  • All tests passed. If this feature is not already covered by the tests, I added new tests.
  • This pull request is on the dev branch.
  • I used npm run format for formatting the code before submitting the pull request.

This PR builds on top of the existing work by @davidcorrigan714 done in PR #495 by adding support for OpenID Connect into the Azure DevOps extension and fixes issue #494.

As part of the PR, me and my team (@davidwinslowtech @HenrikStanley and @NimaZahedi) have implemented the following:

  • Support for choosing OpenID Connect as the Authentication method for all 4 types of Service Connections.
  • Documented how to use this new feature in the README file.
  • Cleaned up inconsistent use of help text in the Service Connections (made all sample URLs be the newer https://my.jfrog.io instead of https://repo.jfrog.org) to conform our changes with the latest help text on newer tasks.

In regards to testing, it is not feasible for us to create tests for this feature as it relies on calling the IdTokens which can only be done from the Azure DevOps pipeline as the IdToken has to be obtained from an Azure DevOps build context as part of how the security and authentication flow works. If tests for this is required we would suggest that the JFrog maintainers creates integration tests for this in their Azure DevOps pipeline setup.

Since these tokens are only available in a built context, a known limitation is also that the Task Preview feature you get when editing tasks inside of the Azure DevOps pipeline editor, cannot authenticate to the JFrog instance from that environment and get a list of available repositories etc, as the token is only valid in the context of a pipeline run.

We have done fairly extensive manual testing of the feature.

@github-actions
Copy link

github-actions bot commented Nov 6, 2024

CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅

@HenrikStanley
Copy link
Author

I have read the CLA Document and I hereby sign the CLA

@HenrikStanley HenrikStanley changed the title feat: Adding oidc implementation for service connections. feat: Adding OpenID Connect (OIDC) implementation for Service Connections. Nov 6, 2024
@HenrikStanley
Copy link
Author

recheck

@yahavi yahavi added the safe to test Approve running integration tests on a pull request label Nov 6, 2024
@davidwinslowtech
Copy link

I have read the CLA Document and I hereby sign the CLA

@nicornk
Copy link

nicornk commented Dec 6, 2024

We are a customer of both Azure DevOps and JFrog and would appreciate if this would be merged an published! thanks for the contribution...

@tiwarishrijan
Copy link

When can this PR be merged ? We are using both AzDo and Jfrog and this feature is very much needed to avoid token management.
Thanks in advance !

@EyalDelarea
Copy link
Contributor

Hey @HenrikStanley, thank you so much for this amazing PR!

Apologies for the delayed response — we truly appreciate your contribution. 🙏
We’ve recently made some updates to OIDC support in the JFrog CLI, and your work aligns perfectly with those changes.

We’ll build on top of your PR and incorporate the latest improvements. I’ll keep you posted here as we move forward.

Thanks again for this valuable contribution — really great work!

@HenrikStanley
Copy link
Author

Seems like the support has finally been added in PR #533
And released in https://github.com/jfrog/jfrog-azure-devops-extension/releases/tag/2.11.0

I am closing this PR :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

safe to test Approve running integration tests on a pull request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants