Can't access to Tempo Authorize page via OAuth 2.0

Hello there:

I have a .NET Core app that connect both, Jira Cloud and Tempo, to get Issues and Employee worklogs info. It works fine in the past, but now is not working.

I know Tempo is being migrated to Forge, but i tried to change the URL to get app authorization to:
https://api.tempo.io/oauth/authorize/redirect?client_id=$CLIENT_ID&redirect_uri=$REDIRECT_URI&jira_url=https://{jira-cloud-instance-name}.atlassian.net
But it tries to connect to the older URL:
https://{jira-cloud-instance-name}.atlassian.net/plugins/servlet/ac/io.tempo.jira/oauth-authorize/?client_id=$CLIENT_ID&redirect_uri=$REDIRECT_URI

I think it's because it's still in migration process, but it keeps saying the same error:

“Se ha producido un error por nuestra parte.

Si el problema persiste, comparte esta información con tu administrador, que debería contactar con el servicio de soporte.”

I tried changing the authorization code with a new one, both Jira and Tempo, expecting an out of date one, but no, it keeps saying the same error.

Shall I wait to the end of migration or there is an error in my code?

Thank you.

3 answers

Suggest an answer

0 votes

This is weird. I tried again and still the same problem.

But, when it loads the Atlassian page, then the sidebar applications, and then the error, if I copy the URL (the new one from my code, or the older one from the error window) and paste on a new tab, then it works properly.
I tried some solutions, like changing RedirectResult for Redirect, then with:

return Content($@"
<html>
<head>
<script>
window.top.location.href = '{tempoUrl}';
</script>
</head>
<body>
Redirigiendo...
</body>
</html>", "text/html");

All gave me the same problem. Then I put:

return Content($@"
<html>
<body>
<a href='{tempoUrl}' target='_blank'>
Login con Tempo
</a>
</body>
</html>", "text/html");

And it works with a manual click. Is it normal?

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

0 votes

@Carlos A_ López Ortín

Contact with Support from Tempo. Migration shouldn´t influence that.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

0 votes

Hi @Carlos A_ López Ortín
It doesn’t seem like there is anything wrong with your implementation. Tempo is migrating OAuth to the Forge platform, and this causes some issues during this process that make the application return this error since it redirects you to the authorization URL for the previous platform.

Since you’ve already regenerated the credentials and changed the authorize URL to the new one, the problem could be on the Tempo side or with their migration process regarding your site’s instance.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Was this helpful?

Thanks!

App Central

DEPLOYMENT TYPE

CLOUD

PRODUCT PLAN

STANDARD

Forums

Q&A

Community resources

Support

Top groups

Community resources

Support

Learn

Community resources

Support

Events

Community resources

Support

Can't access to Tempo Authorize page via OAuth 2.0

3 answers

Suggest an answer

Was this helpful?

Thanks!

DEPLOYMENT TYPE

PRODUCT PLAN

TAGS

Atlassian Community Events