Atlas links in Confluence - This integration requires storage access

[Lauren Cooper]

Recently I started getting this message in all my Atlas embedded links in Confluence (never used to)

I can click on Authorize so I can see the link content, but it is only temporary.

Any changes made to the page or view take it back to this message again.

Any ideas?

[Matthew McGarity]

It has to do with third-party cookies, specifically how one being set on team.atlassian.com is not persisting thru to the iframe being displayed within *.atlassian.net. I've got a support case open to further discuss this.

I'm a Safari user and refuse to disable my third-party cookie settings. I've had better luck using Chrome to persist this cookie, which makes me concerned about what's happening while using that browser.

[Justin Waugh]

Having the same issues on Chrome. 

[Mark]

Hi Lauren,

As per Matthew's excellent response above - this issue is due to cross-site cookies, and typically due to Safari's strong stance in blocking them. We're actively looking into solutions to this problem but alas for now you will need to re-authorise unless you change your cookie settings.

Thanks,

Mark

[Lauren Cooper]

 @Mark  @Matthew McGarity  I am using Edge and I don't have third-party cookies blocked. 

  

And I have also just added [*.]atlassian.net to my Allow list.

  

I've even cleared my atlassian.net cookies and started again.

What is strange is I didn't use to have a problem. It just started one day.

Thanks, Lauren

[Ben McCormick]

I'm also seeing this in Jira, using Chrome without blocking cookies.

When I click the authorize button AFAICT nothing happens, there is no network request that goes out, and the message remains

[Beatrice Glienke]

same with me, using chrome.

[Jo-Lee Bertrand]

Same for me, also using Chrome

[Omer Meshar]

Same for me, using Chrome

[Ash Ahmad]

Hey @Beatrice Glienke @Jo-Lee Bertrand @Omer Meshar @Ben McCormick  @Lauren Cooper

Could you let me know if this is still happening for you, please?

We've pushed up a change that should resolve this issue, but it still might fail for some people. If Chrome/Edge (v113 or newer) thinks you have ever denied the prompt that shows up when you press "Authorize" then it bugs out if we try to ask you for permission again. If you fall into that bucket, enabling third-party cookies should now be a reliable work-around for that while we figure out how we can improve this further. If you do still get an error, let me know what you're seeing and I'll look for another solution.

[Jo-Lee Bertrand]

@Ash Ahmad Seems to be working for me now! Will continue to watch over next little while. Thank you! This was critical for us to expand adoption of Atlas.

[Lauren Cooper]

@Ash Ahmad It also seems to be working for me! Thank you for sorting.

[Omer Meshar]

Works for me as well, thanks.

[Ben McCormick]

Resolved for me, thank you!