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

Question

Question

User with Full LFDS license type reflecting retrieval license in repository

asked on May 11

I have a user who - as of this morning . cannot log into the repository with his prior read/write/modify permissions using his Active Directory (AD) credentials.  All documents are being returned as "read-only."   Other users are not reporting this issue.

 

I pulled apart his configuration to verify if it is an issue with his group membership (LFDS, Repository), his LFDS license type and any additional settings which might return him to a read-only access.   Nothing was found.

 

When I checked the group level permissions, they were as expected.   Read/write/modify.

 

I deleted his account in LFDS and in the Repository and then re-added them back.  I synchronized in LFDS with Active Directory

 

In both the Web Access/Admin Consoles, he shows as a read-write user.  In LFDS, he shows with a Full License.  However, when he logs in - his account is reflecting a "Retrieval User" versus a "Full User"

 

In the TEST server, his account is correct.

 

Any ideas?

0 0

Answer

SELECTED ANSWER
replied on May 12 Show version history

Thank you for replying.  

The issue is resolved.   Indeed it did have to do with a read-only group.  I had verified that prior to raising the question on the forum.  What made this specific issue different is that the user was not a member of any read-only groups, but there was a read-only group nested within a general access group.   After changing the permissions of the group and then adding security at the folder level, user functionality was restored.  What made this especially confusing is that another user - in the same grouping - was not experiencing issues.   

Thank you.

0 0

Replies

replied on May 12

If the account is working correctly in the test repository, it is more than likely a setting in the production repository. Either a group or user setting within the repository itself.

0 0
replied on May 12

Check out any groups that user is  a member of, especially within the repository. If any of them are set to "Read Only", all members of the group will always log in read-only.

0 0
SELECTED ANSWER
replied on May 12 Show version history

Thank you for replying.  

The issue is resolved.   Indeed it did have to do with a read-only group.  I had verified that prior to raising the question on the forum.  What made this specific issue different is that the user was not a member of any read-only groups, but there was a read-only group nested within a general access group.   After changing the permissions of the group and then adding security at the folder level, user functionality was restored.  What made this especially confusing is that another user - in the same grouping - was not experiencing issues.   

Thank you.

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

Sign in to reply to this post.