Document how to pass restrictive validation by providers

Question

Document how to pass restrictive validation by providers

Opened this issue a year ago · 6 comments

It takes a lot of time and proof to to get credentials for providers like Facebook/Instagram and Google.

We should research if we can smoothen this process for the majority of users by providing some kind of report on Companion, which shows things like security vulnerability checks.
Document that it can take up to 8 weeks to get through the process for Drive. Also document the duration for other providers.
Document how users can go immediately to production with Transloadit provided credentials.

Answer 1 · 2024-08-19T02:32:51.000Z

Hey @Murderlon, just wondering if there was any progress with this?
We're in the process of verification, they have just requested the CASA assessment.

Thank you, guys.

Answer 2 · 2024-08-19T07:18:50.000Z

For Google Drive we are building a new plugin which would use the Google Driver Picker UI, which significantly reduces the verification process.

Answer 3 · 2024-08-20T01:19:04.000Z

For Google Drive we are building a new plugin which would use the Google Driver Picker UI, which significantly reduces the verification process.

Awesome, is there an ETA on that? Don't want to be pushy, is just to see if I should give it a go myself (we had to remove the Google Integration as we missed the notifications from Google) or better to wait until you guys have it.

Thank you for your amazing work.

Answer 4 · 2024-08-20T08:25:23.000Z

It's one of higher priorities now since Transloadit is currently also suffering from the verification process and we don't want downtime. However, it's still being worked on with limited hours available so it could still be two weeks or so.

Answer 5 · 2024-11-05T04:36:57.000Z

We've been denied by Google for the drive.readonly scope so we are keen to see this completed

Answer 6 · 2024-11-05T08:53:16.000Z

The way I understand it now, from our own experience going through the process again, is a guide by us isn't going to help much, you still have to get a security audit by a third party. Google is being hostile against developers wanting to use their integrations and the only 'happy path' is using their Google Picker API, which reduces the scope and therefor the requirements.

There is an open PR for using the Picker frontend from Google transloadit/uppy#5443