Skip to content
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

[Identity] Callback design for service connection support for Workload Identity Federation #29349

Closed
wants to merge 20 commits into from

Conversation

KarishmaGhiya
Copy link
Member

Packages impacted by this PR

Issues associated with this PR

Describe the problem that is addressed by this PR

What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?

An alternative design to this PR - #28628

Are there test cases added in this PR? (If not, why?)

Provide a list of related PRs (if any)

Command used to generate this PR:**(Applicable only to SDK release request PRs)

Checklists

  • Added impacted package name to the issue description
  • Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
  • Added a changelog (if necessary)

@Penguinwizzard
Copy link

What's the point of this over ClientAssertionCredential? You're basically just providing a client assertion callback - I don't see why it needs its own credential type after this. Further, if we're going to go this far, why not make ClientCertificateCredential also just provide a callback that can be used with ClientAssertionCredential?

@azure-sdk
Copy link
Collaborator

API change check

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

@azure/identity

@@ -84,15 +123,21 @@ export class WorkloadIdentityCredential implements TokenCredential {
*/
public async getToken(
scopes: string | string[],
options?: GetTokenOptions,
options?: GetTokenOptions
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should there be a call to the callback in here somewhere? I don't see it being called anywhere yet, wondering what the end state you expect is.

@KarishmaGhiya
Copy link
Member Author

Closing in favor of #29392

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

Successfully merging this pull request may close these issues.

4 participants