Is it possible to use the A2A with another service than Gemini? I'm stuck on this step:https://support.atlassian.com/security-and-access-policies/docs/manage-a2a-connections-in-admin-hub/"Users must complete OAuth 2.1 authorization before Gemini can call Rovo on their behalf. More information on the setup ."
I need the agent communication url, client id, and secret. I'm assuming something is hard coded to Gemini?
Does this article apply to A2A or only mcp? https://support.atlassian.com/atlassian-rovo-mcp-server/docs/configuring-oauth-2-1/
Hi @Austin Scott
No, not out-of-the-box today.
If you are using Gemini: Don't search for static OAuth Client IDs/Secrets. Go to the Google Cloud Marketplace, install the Rovo Agent listing, and complete the OAuth consent prompt in your browser. See Rovo-Gemini-marketplace
If using non-Gemini : Switch from the A2A tab to the Atlassian Rovo MCP Server setup, which supports OAuth 2.1 PKCE and API Token authentication for non-Gemini clients. See Github-atlassian-mcp-server
We tried implementing the A2A integration by connecting our LangChain agent through A2A with Atlassian Rovo. Rovo is able to retrieve the Jira spaces, but it cannot retrieve specific Jira work item details. We faced the same issue during our initial testing. Has anyone else experienced this limitation with A2A and Rovo?
Yes, this is a very common hurdle when getting started with A2A (Agent-to-Agent) integrations between Rovo and external agent frameworks like LangChain!
By default, the A2A protocol’s request payload sends high-level context metadata. It does not automatically embed the full work item details into the message payload.
The intended pattern is for your remote agent to fetch the deep work item data on demand via Jira's REST API.
It looks like you're new here. Sign in or register to get started.
