I've recently run into a hitch while developing live content previews for the blocklist editor, specifically when I am fetching content such as images using the mediaResource or entityResource from the backoffice API.

I broadly followed the example in the Blocklist editor deep dive article and this works fine for most users but for anyone setup as a Writer it kicks them out of the backoffice with a 401 unauthorised error whenever they try to edit the page containing that blocklist editor.

I had a similar experience fetching a list of content types from the contentResource which even booted out users setup as Editors!

I feel sure there must be a way around this otherwise lots of other plugins/packages would be failing for users with lower privileges.

Thanks

Chris