[#680] Resolve appId in agentResponseHandler#698
Merged
tracyboehrer merged 3 commits intomainfrom Oct 20, 2025
Merged
Conversation
tracyboehrer
approved these changes
Oct 20, 2025
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
2 participants
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.
Fixes #680
Description
This PR updates the handleResponse function in AgentResponseHandler to get the host's appId from the agent's default connection.
Additionally, it fixes an issue in the agent-to-agent communication. The second agent was receiving the activities without the authorization token. We fixed this by passing the authConfig when calling the postActivity.
Also, we added a condition to allow anonymous authentication between agents when no token is provided.
Testing
These images show the RootAgent and EmptyAgents communicating with each other using credentials and anonymous auth.
