[OCISDEV-554] Password protected share gets authenticated twice

[jvillafanez]

Describe the bug

When you try to access to a public share and enter the password, the request is sent twice

Steps to reproduce

1. Create a password protected public share
2. Try to access the share from another browser
3. Enter the password. It doesn't matter if it's correct or not.
...

Expected behavior

Only one request to access the password is made

Actual behavior

2 requests are made.

Setup

- Web version:
- oCIS version:
- browser:

OCIS_XXX=somevalue
OCIS_YYY=somevalue
PROXY_XXX=somevalue

Additional context

No response

[existentialcoder]

Do you think I can pick this up? Trying to look for a good first issue and thought this was ideal

[LukasHirt]

@existentialcoder sure, feel free to take this up. Thank you and please, let us know if you would need any support.

[existentialcoder]

@existentialcoder sure, feel free to take this up. Thank you and please, let us know if you would need any support.

Hello @LukasHirt. Sorry for the delayed response.

I just got chance yday to try and setup and have been facing this issue. Using the default credentials of katherine

Getting 401 error for the below endpoint.

https://host.docker.internal:9200/api/v0/settings/roles-list

My env

OS - WSL2 Ubuntu 22.04
node version - 24
Docker env - Docker desktop

Logs from the docker container

web_ocis  | 2025-12-18T11:29:16Z ERR failed to authenticate the request error="failed to verify access token: 404 Not Found: 404 page not found\n" authenticator=oidc client.address=172.18.0.1 network.peer.address= network.peer.port= path=/ocs/v2.php/cloud/capabilities service=proxy user_agent="Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/143.0.0.0 Safari/537.36"
web_ocis  | 2025-12-18T11:29:16Z ERR failed to authenticate the request error="failed to verify access token: 404 Not Found: 404 page not found\n" authenticator=oidc client.address=172.18.0.1 network.peer.address= network.peer.port= path=/api/v0/settings/roles-list service=proxy user_agent="Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/143.0.0.0 Safari/537.36"
web_ocis  | 2025-12-18T11:29:16Z ERR failed to authenticate the request error="failed to verify access token: 404 Not Found: 404 page not found\n" authenticator=oidc client.address=172.18.0.1 network.peer.address= network.peer.port= path=/graph/v1.0/me service=proxy user_agent="Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/143.0.0.0 Safari/537.36"
web_ocis  | 2025-12-18T11:29:17Z ERR failed to authenticate the request error="failed to verify access token: 404 Not Found: 404 page not found\n" authenticator=oidc client.address=172.18.0.1 network.peer.address= network.peer.port= path=/ocs/v2.php/cloud/capabilities service=proxy user_agent="Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/143.0.0.0 Safari/537.36"
web_ocis  | 2025-12-18T11:29:17Z ERR failed to authenticate the request error="failed to verify access token: 404 Not Found: 404 page not found\n" authenticator=oidc client.address=172.18.0.1 network.peer.address= network.peer.port= path=/api/v0/settings/roles-list service=proxy user_agent="Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/143.0.0.0 Safari/537.36"
web_ocis  | 2025-12-18T11:29:17Z ERR failed to authenticate the request error="failed to verify access token: 404 Not Found: 404 page not found\n" authenticator=oidc client.address=172.18.0.1 network.peer.address= network.peer.port= path=/graph/v1.0/me service=proxy user_agent="Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/143.0.0.0 Safari/537.36"

Running the setup with the out-of-the-box docker compose file. and doing a pnpm build:w for frontend. Attaching the har file for your reference.

Trying to understand if there are any known issues or prerequisites for wsl before trying to debug further myself. Thanks :)

[LukasHirt]

@existentialcoder there is one known issue with build on Windows but looks like it does not affect wsl since you have been able to build the frontend. I am not aware of any other known issue. However, I do not know whether someone already tested the setup using wsl.

In general, there should not be any prerequisite other than setting up the host.docker.internal alias. I will try to see if I can spin up the same environment to debug this as well.

[existentialcoder]

@existentialcoder there is one known issue with build on Windows but looks like it does not affect wsl since you have been able to build the frontend. I am not aware of any other known issue. However, I do not know whether someone already tested the setup using wsl.

In general, there should not be any prerequisite other than setting up the host.docker.internal alias. I will try to see if I can spin up the same environment to debug this as well.

There were problems with my wsl networking and I had to reinstall, setup host.docker alias and it worked. I have raised the PR for the fix. Let me know if this would work. Thanks