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

Search is available but doesn't work for authenticated user on the public link page #10915

Closed
ScharfViktor opened this issue May 16, 2024 · 10 comments · Fixed by #10928
Closed
Assignees
Labels
Priority:p3-medium Normal priority Type:Bug Something isn't working

Comments

@ScharfViktor
Copy link
Contributor

Version | 5.1.0-prealpha+0ac03d8a8
web 9.0.0-alpha.5

Steps:

  • create folders f1
  • create link to the folder f1
  • login in as marie and open link

Actual:

  • Search is not available for public but what should we do if authenticated user? show or not search line?
  • Search doesn't work - 401 Error
Screenshot 2024-05-16 at 08 16 22

Expected: ? @kulmann maybe you have idea, what should we expect here?

@ScharfViktor ScharfViktor added the Type:Bug Something isn't working label May 16, 2024
@ScharfViktor ScharfViktor changed the title Search is available for authenticated user on the public link page Search is available but doesn't work for authenticated user on the public link page May 16, 2024
@kulmann kulmann added the Priority:p3-medium Normal priority label May 16, 2024
@kulmann kulmann moved this from Qualification to Prio 3 or less in Infinite Scale Team Board May 16, 2024
@kulmann
Copy link
Contributor

kulmann commented May 16, 2024

Nice finding! I'd expect that the search input is visible ( ✅ ) and that it works ( ❌ ) as this is an authenticated context. IMO the fact that the view being displayed belongs to a public link is not relevant for the rest of the screen layout (search, app menu, user menu, left sidebar nav).

@ScharfViktor
Copy link
Contributor Author

I'd expect that the search input is visible ( ✅ ) and that it works ( ❌ ) as this is an authenticated context

yeah, search should work, thank you 👍
but the search result never gets to Marie the result which related to the public link
Screenshot 2024-05-16 at 09 25 08

this can be confusing to the user. Maybe there's some way we can let the user know about it.

@AlexAndBear AlexAndBear self-assigned this May 16, 2024
@AlexAndBear
Copy link
Contributor

I am currently on master branch and admin shared a link. I login as Alex and open the public link from admin as soon I enter the password, I see the content and the search. I can hit the search and I will be able to find results.

Am I getting something wrong here, because it's not reproducible for me...

image

@ScharfViktor
Copy link
Contributor Author

Am I getting something wrong here, because it's not reproducible for me...

I tied reproduce again. I can reproduce.

@AlexAndBear
Copy link
Contributor

Can you check on web master with latest ocis ? it works for me

@ScharfViktor
Copy link
Contributor Author

@ScharfViktor
Copy link
Contributor Author

Can you check on web master with latest ocis ? it works for me

all fresh

@AlexAndBear
Copy link
Contributor

We found the issue, this is happening because we are sending the basic auth header instead of the bearer token while doing the dav report request.

@ScharfViktor suggested disabling the search entirely when we are in a public link (context), because it will eventually be confusing to the user, that they can't search in the link but the personal space and other places

any opinion @kulmann @tbsbdr ?

@kulmann
Copy link
Contributor

kulmann commented May 16, 2024

Good finding! No hard feelings. Fine by me to disable the search in that case 👍

@AlexAndBear
Copy link
Contributor

I take over and remove it in this context as I think @ScharfViktor s
considering is valid

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority:p3-medium Normal priority Type:Bug Something isn't working
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants