cancel
Showing results for 
Search instead for 
Did you mean: 

No user CIFS access to RM documentLibrary

mathgallant
Champ in-the-making
Champ in-the-making
Hello,

Using Alfresco 3.3g with RM module. I cannot get "Records Management User"s to be granted access to the rm site documentLibrary. Actually, I can't get anyone who is not an Alfresco Administrator to be granted access to it. I am focusing on the "Records Management User" group for now.

I have found references on the boards that suggested that I need to add the RM group (the "Records Management User" in my case) to the rm site (as a consumer, again in my case), that didn't help (my user was a member). I also added specific users to the permission option of the series in the file plan (read-only in my case), didn't help either. I then tried to add the user as a consumer to the site, which also didn't help. Any combination of the above does not help.

Things I find odd which may indicate a problem to the trained eye :
- The User Rights Report in the Records Management Console says that there are no groups available
- Seems I only need to add my user to the "Records Management User" in Alfresco Explorer in order to be able to browse the File Plan with proper access rights. No need to join the site and no need to add a user or group to the site either. Just add the user to the "Records Management User" group and grant access to that user to the specified item in the file plan. (this is odd in the sense that it indicates that things should work fine)
- I cannot add groups in the permission option of an item in the File Plan (only users show up)
- If I am not a member of any Record Management Group, the documentLibrary link in CIFS does not show up (as expected, so it does seem like groups are taken into account).
- Alfresco Share Sites documentLibrary work just fine.

When I get denied access in CIFS, I get nothing in the logs.

I really don't know what the problem could be.

Thanks for any help.
3 REPLIES 3

mathgallant
Champ in-the-making
Champ in-the-making
Tried again with 3.4b. No access using CIFS.

This is a fresh install, authentication using passthru. This time around the RM sees groups, but it does not change the fact I can't access the RM site using CIFS.

mathgallant
Champ in-the-making
Champ in-the-making
Well I managed to grant permission on the documentLibrary to other users in 3.4b using the "repository" link in Share. I navigated to the RM and edit the permissions for the documentLibrary (need to show folders). I clicked "inherit permissions" and now the RM groups can access the RM documentLibrary (I still need to set permission on individual items in the library, but thats fine).

I imagine this is done using alfresco Explorer in 3.3g since there is no "repository" link in the top toolbar in share in this version.

mathgallant
Champ in-the-making
Champ in-the-making
Just to add a little more information on the issue. CIFS seems all messed up. It doesn't work at all on 3.4b as I can't write to it no matter what. 3.3g works fine outside of the RM site.

Seems adding users to the site alone does not work in a RM site as permission are not inherited and therefore members of the site have no rights that extend to the documentLibrary. This is by design, or so I read on the forum. I can either force permission inheritance or add specific site permissions on objects in alfresco explorer or using the "Repository" management tool in 3.4b, but, unfortunatly, while I can access the RM documentLibrary in CIFS this way, I still can't write to it. Could be an unrelated issue.

Setting permissions in the fileplan using the "Manage Permissions" link only adds "file" and "Read" permissions. Those permissions are ok for user going through the Share interface, but are not appropriate for going through CIFS (so it seems).

Those permissions seem to conflict with something when copying documents into a folder in the Fileplan using CIFS as the document gets created, but no data can be added to it (remains at 0 bytes). This happens in 3.4b and 3.3g. It can't be modified or deleted no matter what permissions the user has (except for administrators).