Tempo API and redirect URIs

[Filipe Colaço]

I am developing a connector between Jira's Tempo app and an ERP system (Odoo).

I configured our OAuth 2.0 Application and am attempting to use the following redirect URI for the callback when fetching the authorization code: "https://<company_domain>/jira/auth_code?integration_id=1&user_id=2"

Given this, I have two questions:

1. I've realised that the application's redirect URI and the authorization call's redurect URI must be the same, otherwise the authorization screen will say "Could not finish authorization: redirect uri is invalid". Is this really the case? As you'll see from my URI I need to pass a couple parameters to process the callback and these are dynamically generated.

2. I believe that the introduction of the ampersand on the URI is messing up the URI parsing on Jira's side. I tried only "https://<company_domain>/jira/auth_code?integration_id=1" and it worked fine, but with the complete URI it doesn't.

What are my options for both cases?

[Martin Runge]

Hi @Filipe Colaço

Welcome to the Atlassian community!

I would resolve this by passing your dynamic tracking IDs in the standard OAuth state parameter instead of appending them directly to the callback path, because the redirect_uri requires an exact character match to validate safely. Has this issue already been solved for your integration in the meantime?