Add support for passing access tokens to com.azure.security.keyvault.jca for use in Azure devops

[woerdeka]

Description

• Added the "azure.keyvault.access-token" parameter to the com.azure.security.keyvault.jca library allow one to pass an access token directly. This way, it is possible to use

( az account get-access-token --scope https://vault.azure.net/.default | ConvertFrom-Json ).accessToken

to obtain an access token for accessing a keyvault, and pass that to the signing library. This is needed to be able to use federated authentication with service connections in Azure devops.

All SDK Contribution checklist:

• The pull request does not introduce [breaking changes]
• CHANGELOG is updated for new features, bug fixes or other significant changes.
• I have read the contribution guidelines.

General Guidelines and Best Practices

• Title of the pull request is clear and informative.
• There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

• Pull request includes test coverage for the included changes.

[github-actions]

Thank you for your contribution @woerdeka! We will review the pull request and get back to you soon.

[azure-sdk]

API change check

APIView has identified API level changes in this PR and created following API reviews.

com.azure:azure-security-keyvault-jca

[woerdeka]

@microsoft-github-policy-service agree company="Keenfinity Group"

[woerdeka]

I really don't understand what is causing the build errors. It does not seem to be related to my changes.

[microsoft-github-policy-service]

@woerdeka the command you issued was incorrect. Please try again.

Examples are:

@microsoft-github-policy-service agree

and

@microsoft-github-policy-service agree company="your company"

[woerdeka]

@microsoft-github-policy-service agree company="Keenfinity Group"