Redirect to Login Mask for Read Only Users

[cmprmsd]

Steps to Reproduce

• Create a LaTeX document
• Invite someone with "Read Only" permissions
• Accept the invite and open the report as invited user

Expected Behaviour

The page should now redirect you to the report and view it.

Observed Behaviour

The user will see the loading Overleaf icon and then there is a redirect to the login mask, although the user is logged in.

Context

Users cannot see the document I want them to be able to see.

Technical Info

I'm using the dockerized version with nginx and websockets enabled.
Please refer to overleaf/web#760 for more screenshots and technical details.

[cmprmsd]

Hey :)
I'd love to help fixing this issue.
What do I need to provide?

[salleman33]

Hi,
you could try to set environment variables SHARELATEX_ALLOW_PUBLIC_ACCESS and SHARELATEX_ALLOW_ANONYMOUS_READ_AND_WRITE_SHARING to 'true'

[cmprmsd]

Hey, thanks for your help.
I'm not sure if we want to go that route though.
We only want access for people with account to ensure the link will not be reshared with third parties.

From what I understand it is one resource that sometimes returns with 403 forbidden and then the login mask will be presented. When we click "back" in the browser history several times, that error will randomly not happen and the document is displayed correctly. However, this is not the way the users will expect or accept as often it will just not work for plenty of tries.

Please see also the traffic screenshots from my referenced issue in the first post.

[salleman33]

ah ok I did'nt understand your problem sorry :/

[cmprmsd]

Still needing help on this one 😅

[das7pad]

Hello,

Thanks for raising this issue. I'm sorry it took this long for replying here. A lot has changed since 2021, we've fixed a few bugs in the editor that were triggering requests that resulted in authorization errors, which in turn triggered the redirect to the login page.
Our newly added automated End-To-End tests for Overleaf Community Edition and Server Pro are opening projects and interacting with the editor, which should avoid regressions here.
Let us know if you are still seeing this with the latest release line (version 5.x).

Greetings,
Jakob