Office Integration Security Requirements

asked on March 30, 2017

We ran into a scenario today where we have a workflow running, while the document is being routed around for approvals we house the actual document in a "Routing" folder, and we pass shortcuts to people to approve. We set security on routing folder to allow full access but we take away the Browse right so people can't go into the folder and mess with other peoples documents.

The issue we ran into, is that when we passed a shortcut to the doc, and it was an office document, they opened it to use the office integration to approve, but it immediately gave us a "Permission Denied" error.. with the following details.

Permission denied.

at LFSO102Lib.ILFDatabase.GetEntryByPath(String Path)
at Laserfiche.OfficePlugin.Connector.LFSOImpl.LFSOConnector.GetEntry(String path)

If i add browse back everything functions as normal. I guess i'm wondering

1. Is this an issue or intended to function this way for some reason?

2. Are there any sort of workarounds? I need the docs to remain in the routing folder, and i need them to not see the folder itself.

Thanks in advance!

~Brandon

0 0

replied on March 30, 2017

Hi Brandon,

When you removed browse, did you scope it to JUST the folder ('this entry only') or did it inherit down to include the child documents as well. If you do it to just the folder, does it make the issue go away? People will still be unable to browse to that location in the folder tree.

0 0

View 1 previous reply

replied on March 31, 2017

We just scoped it down from the folder level. We split out the security into 2, one this entry only on the folder removing the browse right, and one Subfolders and documents only that has the Browse right, and that seems to have worked for us. Thanks for the workaround!

0 0

replied on March 31, 2017

Scratch that, i was still getting browse rights on the test user i had.. Ran the test again and still getting the permission denied.. I have full rights on the document except Browse, and i'm still running into the issue.. Any other ideas?

0 0

replied on March 31, 2017

Ok, jumped the gun a bit, was able to give the users rights including browse, but then went in and put a security tag on the folder to hide it from the users. This was allowed to work properly using the Office integration..

0 0

replied on March 31, 2017

You should still have Browse on the document itself. The idea is to remove Browse from the Folder but to leave it on the document.

0 0

Question

Question

Office Integration Security Requirements

Replies

Sign in to reply to this post.