Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Redirect to Login Mask for Read Only Users #939

Open
cmprmsd opened this issue Aug 10, 2021 · 5 comments
Open

Redirect to Login Mask for Read Only Users #939

cmprmsd opened this issue Aug 10, 2021 · 5 comments

Comments

@cmprmsd
Copy link

cmprmsd commented Aug 10, 2021

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
Copy link
Author

cmprmsd commented Aug 26, 2021

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

@salleman33
Copy link
Contributor

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

@cmprmsd
Copy link
Author

cmprmsd commented Sep 6, 2021

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
Copy link
Contributor

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

@cmprmsd
Copy link
Author

cmprmsd commented Dec 7, 2021

Still needing help on this one 😅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants