In Step 6, you should immediately be sent to the page that asks you to verify/accept scopes of your OAuth 2.0 application, instead of just taking the user to the home page of their Airtable account. The current behaviour causes problems for implementations/consumers of Airtable OAuth 2.0 that expect to be able to complete the authorization flow by only initiating the request in Step 1 once.
Hi @ashtontito ,
Thank you for the detailed reproduction steps and screenshots about this issue! I'm an engineer on the API team at Airtable, this is unexpected behaviour that we are now looking in to. I believe it is the same as the issue that @Ian_Erickson posted about here: https://community.airtable.com/t5/development-apis/oauth-flow/td-p/138715
As mentioned in that thread, the temporary workaround would be to ask users to log in to Airtable before starting the flow.
I will keep you updated on our investigation, though as it is now the holiday period, it will take us some extra time to address.
Thanks for the extra info, that context definitely helps us understand how this issue impacts your use case. Excited to hear about your new Airtable Connector too!
We haven't been able to start work on this item yet. I'm not able to give a definite timeline on when it will be fixed but it is on our backlog for the next month - will keep you updated as we make progress.
Hi @ashtontito, we are still working on investigating this issue. If it isn't too much trouble, would you mind shooting us an email at email@example.com (with ATTN "Danny DSE") so that we can request some more diagnostic details? If possible, we'd like to see a screen recording of your browser's Developer Network tool while you are experiencing the problematic OAuth integration redirect. After investigating, hopefully we can share a fix ETA with you soon! Thank you.
Thanks for your patience! The team has been able to track down the issue - there is a bug in our redirect after login flow that interacts with how the URL parameters in the authorization URL are defined.
We’ll be looking into fixing this on our end, but for now, you could get around this on your end by making sure to URL-encode the redirect_uri and scope parameters when constructing your authorization URL.
We’ll add a note to our documentation about this as well.
@Emma_Yeap Was testing Airtable API by following the instruction provided inside the documentation.However, while performing oAuth2, I always encounter this error This third-party app failed to properly construct a request to Airtable: failed to include a redirect_uri in the request
I still got the same error despite including the redirect URL along with the request.