Why are Cookies Set in the Response Header of 0auth Flow Missing in URL When Browser Returns, Causing Authentication Flow Failure?

Pipedream handles steps 1-6 for you. You just have to implement step 7 by including the token Pipedream provides:

The end result is Canva providing a user token, not a cookie. Then you can use this user token to perform authenticated Canva API requests.

ok and what is a reasonable time frame to expect the canva app to be developped?

Are you a Business customer? We can help expedite requests. But there’s a queue of request that are worked on daily. You can see the queue here: Component (Source and Action) Backlog · GitHub

Subscribing to that Github issue linked above will give you real time results.

Ok, well that seems like it’s going to take a very long time.

I appreciate your help and I will investigate just moving the backend to heroku where this process should be doable.

Not necessarily! We just can’t provide timelines. But it can take as little as 30 minutes for the basic integration.

cool, well if it happens quickly that will be great, it just looks like there’s a long lineup

going back to your original question - if you open Chrome dev tools and preserve the network log, then kick off the auth flow, are you specifically not seeing the set-cookie header returned from the first request? I’m trying to figure out exactly where the issue is so I was hoping you could help me trace

Ok reading over your original message, I see you do see it in the response. But the browser doesn’t accept / save the cookie?

Are you able to provide the endpoint that I can hit to see exactly what’s happening? Feel free to DM if you need

dm’d thanks