 |
|
 |
Subject: Document Security-You are not authorized |
 |
 |
 |
Product Area: Notes Client |
 |
Technical Area: Security |
 |
Platform: Windows |
 |
Release: 8.5.1 |
 |
Reproducible: Intermittent |
 |
 |
 |
 |
We have a single appliation, a Discussion database, using the StdR85Discussion template. Reader access is give to the database at the ACL level, via groups. Document security is then given to only those groups, or group members, who need access to each particular report.
After quartely reports are posted, Document links are emailed to only the users who should have access to each report document.
Invariably, one or two random users (never the same users) cannot open the reports via the links. They get a "You are not authorized to perform that operation" error. Could be that they have had links to three different reports and only one of them throws this error.
IF we open the application from the same users' Notes client, and open the report document, the report opens; no error. The document links that were emailed will now work.
We have tried:
Removing the user from the group and readding them.
Removing the group from ACL and document security and readding the groups.
Removing the user from the group, removing the groups from ACL and doc security then reversing the process.
Run Fixup -F, Compact -b, Updall -r on database.
Deleted the full text index and recreated.
Run updall -r on the database and the names.nsf on the server, (from a technote).
Deleted the cache.ndk and bookmark.ndk files from the user's client files.
All of our users are roaming and we have tried having the user move to another workstation, same results.
Because this happens to different users each time reports are posted my suggestion to fire the individuals, who get this message, is not practical.
I'm lost. Any ideas what might be causing this?
Most grateful for any recommendations.
 
Feedback number WEBB8PTSKT created by ~Naomi Desvelusonetsi on 12/23/2011

Status: Open
Comments:

Document Security-You are not autho... (~Naomi Desvelus... 23.Dec.11)
. . my guess (~Phil Nonhipige... 3.Jan.12) |
|  |
|