OAuth login works, but some users get "cannot find an account"

Help
1

Hey,

We’re running into an issue with Frame.io OAuth.

If a user already has a Frame.io session in their browser, everything works fine.

But if they aren’t already logged in, they’ll go through the Adobe login flow successfully, get redirected back to our app, and then receive a “cannot find an account” error.

These users do have Adobe accounts, so authentication itself appears to be working. The failure happens afterward when Frame.io tries to find their account.

Is it expected that a user needs an existing/provisioned Frame.io account before OAuth can be used? Or is this a known issue?

Has anyone else run into this?

2

Hi @rodrigo!

Yes, users will need to have an existing Frame.io account prior to authorizing your app. In those cases, it’s expected you would get a 401 error though, so the specific error message you’re seeing points to this being caused by something else.

Question: are you getting any other error codes along with this error message?

Also, what endpoints are you attempting to hit when you run into this error? If the token was issued correctly, and the user does have a Frame.io account, a call to /v4/me should succeed regardless.