You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This showed up in DQL queries: DQL can return note IDs for documents that the executing user can't see, and then loading the document itself with getDocumentById doesn't throw an exception. The exception occurred in the next step: trying to read any value from the document then throws a NotAuthorizedException for "You are not authorized to perform that operation".
Since this is an edge case and the caller often knows when it may occur, it'd make sense to add an OpenDocumentMode flag to implicitly due a secondary check to make sure the document can be opened. Ideally, this check will be a cheap operation that will nonetheless hit this error code.
Unfortunately, in early investigation, it appears that the behavior for this is different when on a local client runtime vs. on a Domino server. In a local test case (even when using a differently-named session), this instead throws "Invalid or nonexistent document" immediately upon trying to open the document.
The text was updated successfully, but these errors were encountered:
This showed up in DQL queries: DQL can return note IDs for documents that the executing user can't see, and then loading the document itself with getDocumentById doesn't throw an exception. The exception occurred in the next step: trying to read any value from the document then throws a
NotAuthorizedException
for "You are not authorized to perform that operation".Since this is an edge case and the caller often knows when it may occur, it'd make sense to add an
OpenDocumentMode
flag to implicitly due a secondary check to make sure the document can be opened. Ideally, this check will be a cheap operation that will nonetheless hit this error code.Unfortunately, in early investigation, it appears that the behavior for this is different when on a local client runtime vs. on a Domino server. In a local test case (even when using a differently-named session), this instead throws "Invalid or nonexistent document" immediately upon trying to open the document.
The text was updated successfully, but these errors were encountered: