Skip to main content

The Miro OAuth flows shows a page on which the user can select the team to which Miro should be installed. Afterwards, the code (and subsequently the access_token) is provided.

Yet, the flow can be only executed once because the “Installed” button isn’t clickable.

This means, in case the application looses the Miro access-token (which I understand from the docu should be cached forever), the user is required to deinstalled the application from Miro and then trigger again the OAuth flow.

 

Hey Ronny, great talking to you again :raised_hands:

We’re working on this issue, though it’s not a hot-fix because it’s about security.

 


Reply