This is a request for improvement.
In short: please consider removing "Access token" from the Miro setup as it seems that it can be retrieved using the other values and currently, providing expired access token results in an unclear setup error.
Details:
We repeatedly tried to configure a connection to Miro and followed the setup instructions to get all the setup values.
However, each time the form saving failed with message:
Validating MIRO configuration and connectivity. Issues found: Received an error while fetching organization data. Please check that the provided company ID is correct and that the provided access token has permissions to read workspace info. Fix issue by following article DATASOURCE_MISCONFIGURED.
It seems I have found a solution, tough: I executed a CLI command
curl --request POST --url 'https://api.miro.com/v1/oauth/token' --header 'Content-Type: application/x-www-form-urlencoded' --data-urlencode 'grant_type=refresh_token' --data-urlencode 'client_id=<clientID>' --data-urlencode 'client_secret=<clientSecret>' --data-urlencode 'refresh_token=<refreshToken>'
which returned a fresh access token, I then saved the fresh access token to the Glean UI of the Miro data source setup, and the form saved.
Since access token can be retrieved using the client id, client secret and refresh token, the setup form should not require the access token.
