The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Status Embed CORP header

Maksim Ikonnikov
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 9, 2022

Hello all,

in our system we have to use cross-origin isolation, including 'Cross-Origin-Embedder-Policy: require-corp' policy.
Therefore when I'm loading Status Embed frame the browser requires 'Cross-Origin-Resource-Policy: cross-origin' header in a response.
It is absent so frame is not loaded.

How is Status Embed supposed to be loaded in this case? May CORP header be added, or we should change something on our side?

Kind regards

 

 

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

1 vote
Jesse Klein
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
November 10, 2022

Hello Maksim,

This is Jesse from the Statuspage support team. Welcome to the community and thanks for reaching out about how you would work with CORP headers. If you are using the recommended status embed then this is not something that can really be changed since it is a pre-built tool.

In your case, it would make sense to create a custom status embed instead. Essentially, it's just calling our Status API and you could modify it from there. Hopefully that is helpful for you on this!

Regards,
Jesse

DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events