And stripe marks those as a failure: Webhooks: what to do when the HTTP status code starts with a three (3xx) : Stripe: Help & Support
Hi @treeder , iiuc the reason you see a redirect is because IDX does not support unauthenticated http(s) access to services running on your IDX workspace. To make it work you will have to configure stripe webhook url by adding an access token query parameter to the webhook url, e.g. like the following:
1234-workspace-domain.cloudworkstations.dev/some/path?_workstationAccessToken=<ACCESS_TOKEN>.
To get the access token, please read this blog post. Namely you can generate it by running the “Generate access token” command in the IDE.
Please let me know if it helps, thanks
4 Likes
I’m sure that will work, but I see that the token only lasts for one hour. Which means I would have to change the webhook URL every hour, not a very optimal dev experience.
Any chance you’ll be adding unauthenticated requests sometime soon? All the other cloud IDE’s I’ve used have this.
Not work with github OAuth login
@Vova I tried accessing my API using this access token method from a client app (browser), but even then I’m getting cors errors.
I think you need to solve this problem before IDX can be used as a proper dev environment. I can’t imagine anyone willing to change URLs every hour AND add some extra cors hacks to their code to try to get around the cors issue.
Any update on non authenticated preview URLs?
Hi @treeder - we are actively working on this right now. There are some changes we need to make across IDX and our underlying VM (which controls ports and their permissions) infrastructure, but we hope to land this soon. (I can give a more exact timeframe when it is about to go into deployment).
3 Likes
Any news on this one @kirupa ?
Yes, we are still working on this actively. If I had to give a loose ETA, I would say by end of month. There are a bunch of loose ends that we need to close from a security point of view, but this is one of our top priorities.
2 Likes
Ok, thanks for the update.