Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This pull request introduces a new
AgenticIdentitymodel to support agent-specific authentication throughout the Teams API client libraries. It refactors authentication and client classes to consistently pass agentic identity information, updates method signatures, and improves extensibility for agent-based scenarios.Agentic Identity Integration
AgenticIdentityclass to represent agent-specific authentication properties and a static method to construct it from a properties dictionary.IHttpCredentialsand related implementations (ClientCredentials,TokenCredentials) to accept and utilizeAgenticIdentityfor resolving tokens, including changes to delegate signatures and method parameters. [1] [2] [3] [4]API Client and Bot Client Refactoring
ApiClient,BotClient,BotTokenClient, andBotSignInClientto accept ascopeparameter and propagate agentic identity information through client instantiation. [1] [2] [3] [4]AgenticIdentitywhen sending HTTP requests, ensuring agent context is included in all relevant API calls. [1] [2] [3] [4] [5]Token and Response Handling
ITokenResponseinterface for token responses and updatedTokenResponseto implement it, improving consistency and extensibility of token handling.Miscellaneous Improvements
[JsonExtensionData]to theAccount.Propertiesproperty to support dynamic extension data in serialization.These changes collectively enable agent-specific authentication flows and prepare the codebase for advanced agentic scenarios in Teams API integrations.