-
Notifications
You must be signed in to change notification settings - Fork 121
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
Unable to Open Document Inside Tagged Folder that has Restricted File Access #1168
Comments
I am seeing the same issue and can provide input. I'm using the docker version of CODE and see these errors in the docker logs.
` |
Nextcloud 19.0.3 I'm running into same issue. Collabora fails to open a file with any restricted tag assigned to it or to parent folder. |
Could you share a screenshot of the affecting flow rule? |
Nextcloud 19.0.3 User is member of group Dev and have no problem opening files from shared folders, but once a folder/parent folder/file is taged with restricted tag, I get the message "Failed to read document from storage" from Collabora |
This is the expected behavior by the files_accesscontrol app: Denying access to foldersThe easiest way to block access to a folder, is to use a collaborative tag. As mentioned in the Available rules section below, either the file itself or one of the parents needs to have the given tag assigned. |
What? I dont get it. If your access to a file has been denied, then of course collabora should not open that file, but our complain was about the time access to a file is granted, but collabora still fails to open that file. Once there is a restricted tag on that file, it just fails to read. Only time my setup works and Collabora does open a file, is when there is no restricted tag anywhere on the path to that file (file/parent/grandparent...) |
Sorry, then I might have misunderstood your comment:
Maybe you can clarify that a bit further then about what folder structure is in place with which tags and which file fails to open. |
Sure. I just tried to create a "Test" folder in the root of "admin" account and created a "New document" named test.odt without any sharing, just a local file. btw. Running all in docker containers, all together with docker compose: Nextcloud 21.0.5 (cloud.domain.com), MariaDB 10.5.12, Collabora Online 4.2.3 connector app, Collabora office 6.4-48 (docs.domain.com) nextcloud error message:
GET /index.php/apps/richdocuments/wopi/files/71746_oc94bwebkvxy/contents?access_token=henNcEX9R10gxvSvNYx8NOPGs6sYcbHH&access_token_ttl=0 |
I just tried the same process with new shiny Nextcloud Hub II (23.0.0) and now called Nextcloud Office. No luck. I even tried using the demo server. No luck there either. Once I put a restricted tag (with a access restriction flow) on the folder where any document I would like to edit resides, Collabora throws the same error. Its frustrating :( |
As I'm blocking access to folders only by the restricted tag, I was able to modify already mentioned flow rule by adding With this modification, Collabora don't have a problem to open files in any subfolders, if the access was not blocked by that flow rule of course. Fortunately, in my case, blocking access on folders is good enough. |
I am having the same issue with NC 27.1.3 In my setup, I want to allow access to word-files, which exist in a groupfolder to only a sub-group. This works very well with restricted file access. When a privileged user now wants to access one of the word-files with collabora, it doesn't work with the same error message as seen above. Unfortunately, I cannot use @MikeK123's workaround with the MIME type, because I need it to filter for word-documents. My workaround now uses the "request remote address": As the access by collabora always comes from the specific IP of the collabora server, I can exclude this IP in the rule and it works fine. Still, it would be nice if this issue could be resolved. Edit: Does anyone know how to configure how to configure ipv4 vs. ipv6 access? It seems to be a little random and so my workaround does not work well because I can either exclude ipv6- OR ipv4-address... |
having the same here. NC29.0.7. file access control rule as follow:
As Bob, member of group "Team B", if I apply the tag "Team B" on a folder, I can navigate into the folder.
no groupfolder, no share, pure personal files. |
Nextcloud 19.0.1
Trying to access documents inside a folder with a Restricted Tag that Blocks File Access (using Flow) to certain users.
Accessed the folder as a privileged user and was unable to open the document.
Error message:
![image](https://user-images.githubusercontent.com/69715968/93667491-f506a000-fab8-11ea-84ee-afaeccadcd97.png)
Nextcloud logs as Admin
![image](https://user-images.githubusercontent.com/69715968/93667503-08197000-fab9-11ea-8770-cc483f3e5dd6.png)
Collabora works fine on other documents that do not have the file access restrictions.
Any solutions to this? How can I help fix this? Happy to post more logs
Reference: #202 - marked as
stale
andwontfix
- However, this problem persists.EDIT: draw.io, a NC extension that edits diagrams work fine in the same environment, so this must be an issue with Collabora.
I need to get this working ASAP in production - any temporary solutions that works while maintaining the folder access control rights?
The text was updated successfully, but these errors were encountered: