You are viewing limited content. For full access, please sign in.

Question

Question

Linking and security

asked on November 29, 2016

So we have a scenario that seemed to have worked in 9 but now no longer works in 10.  We acquired and account that has been linking a documents with different security.  I have been able to reproduce this issue in 10.1 and 10.3.

This may be a case situation but figure I'd ask.  The client currently opens up internal documents and then links them to a Minutes packet.  The Minutes packet is available to internal people and the generic user that Weblink uses.  The internal document is not available to the Weblink user.  When you link to the public document from the private document, the public document becomes unavailable in Weblink.  You also get an error in the Client but can click OK to it.

Error in the Client:

 

Error in Weblink

 

As a separate test I setup two folders, each with a document in them:  Private, Public.  I allowed only myself access to Private and I allowed myself and a coworker access to Public.  I then opened Private and linked to Public.  When I logged in and I had no problems seeing either.  However when my coworker logged in he got the errors.  

Any ideas if this is a change?  Client said this used to work in previous versions as they have thousands of links setup this way already.

Thanks

0 0

Answer

SELECTED ANSWER
replied on November 29, 2016

Hi Chris, this is a known issue; SCR 140055 for your reference. There are actually different errors among the client applications (desktop Client, Web Access, WebLink) for situations where, as you've found:

  1. LF Server is 10.x
  2. Named user has full access rights to Entry1.
  3. Entry1 is linked to Entry2 with a relationship listed as a "Reverse Relationship" in the Admin Console. (e.g. 'Message' instead of 'Attachment', 'Superseded by' instead of 'Supersedes', etc.)
  4. Named user does not have the Browse access right to Entry2.

A fix is still underway as of this reply.

0 0
replied on November 29, 2016

Great James, thank you for the response.  We will keep an eye out for the fix.

Thanks,

Chris

0 0

Replies

You are not allowed to reply in this post.
You are not allowed to follow up in this post.

Sign in to reply to this post.