Hey Rodrigo! We definitely have users with working Jira resources.
For your specific issue, it'll depend on how Jira’s specific access token refresh flow. i.e whether they respond to the request to refresh the token (expected) as a response or if they have a non standard flow to set the token.
I would expect that the refresh flow does not need to be accounted for (i.e should work without whitelisting) but I’d definitely test it to confirm.
Though this approach will probably cause frustration later on when issues arrive, and you’ll have to re-whitelist those IPs whenever you need to re-authenticate e.g to grant new scopes, or when JIRA api runs into issues.
Is there anything I should now to help troubleshoot this issue? I just added the Jira resource, clicked "Connect with OAuth" and gave the necessary permissions.
Hi @victoria , we are experiencing the same problems. The JIRA API is connected to our cloud instance and works perfectly fine, but after a few days we get an authorization error and have to reconnect again. We are using the domain format (api.atlassian...) for connecting just as Rodrigo, so it seems to be the same thing.
Hi Rodrigo and Barbara! Thank you both for surfacing this, happy to look into it with you. Would you mind sharing a screenshot of the errors you're getting? And do you see any errors in your browser console?
Hey Rodgrido! Just spoke with the Workflows team and they confirmed that this is auth related. OAuth is tied to the user, and we currently don't support user-based auth.
We shouldn't be showing user-based auth resources as available to use in Workflows, so we're working on that now!
We do support custom auth only where there is an API request with a time based trigger. The recommendation in this particular case is to not use OAuth, and instead, to use a different authentication scheme if possible...maybe a secret API key w/ scope?
