Creating media atoms from workflow fails with a 403 error

[emdash-ie]

There’s an option in Workflow under Create new in the top-right to create a new Video/Atom. In CODE, filling out the resulting form (with the default Type value of Media) and clicking Create atom results in a POST to https://video.code.dev-gutools.co.uk/api/workflow/atoms which fails with a 403 Forbidden error. There is also no CORS Allow-Origin header on the response.

I have also tested this in PROD, with the same result.

[emdash-ie]

We discussed in planning today: I’ll take a look this sprint to see whether this is also affecting PROD, then we’ll prioritise on the basis of that info.

[emdash-ie]

I tested in PROD just now and got the same error: we can decide how we want to prioritise fixing (or removing?) this in standup tomorrow.

[emdash-ie]

We discussed this in standup today, including mentioning the possibility of fixing the functionality or removing it. We think it’s an auth error rather than a CORS error, so it won’t be as quick to fix as the latter would be, but we’re not really sure.

We’ve decided not to look at this for now, so we’ll return it to the backlog. We can consider it again in future when we take another look at workflow.