This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Filr 23.4 User Web Portal - Net Folders (OES NSS Servers) only available to Filr Admin?

1. In-place upgrade appliances to 23.4 was a success.

2. After upgrade, The Filr Net Folder shares (OES NSS) work fine for the "Admin" user over Web, Windows or Android Filr Clients. They do not work for any other LDAP users that have access to the OES NSS volumes. 

3. Users in question are a part of the "Everyone" LDAP (eDirectory) group or "Administrators" LDAP (eDirectory) group, both of which have access to all of the Net Folder shares in question.

What am I missing?

  • 0

    Reference: https://www.microfocus.com/documentation/filr/filr-23.4/filr-admin/netfolders_global.html

    It's almost as if "Use directory rights in addition to file system rights" isn't enabled, but it is...

  • 0  

    What I would check is that any groups that you use to assign file rights on the file are still imported in Filr and have the membership populated.

    What happens if you give a user explicit rights on the file system?

  • 0 in reply to   

    Good idea. Some notes as I troubleshoot along your line of thinking;

    Administration Console > System > LDAP > LDAP Servers: Sync All runs with no errors (nothing new to sync either though)

    Administration Console > Management > Users: displays all eDirectory users (LDAP).

    Administration Console > Management > Groups: displays all eDirectory groups (LDAP). Membership of every group I check is correct.

    Administration Console > Management > Net Folders > Sync Status: Green check boxes for all listed servers (they are all just in time though)

    I've confirmed eDirectory access rights to both users and groups exist. On this Filr system, we have 18 Net Folder Server Links configured (OES NSS). Not one of them is shown to any user but local Filr Admin. The option to view Net Folders in the User area disappears for every Filr user except for local Admin. I can't shake the feeling here that I'm missing something really obvious, but I might have to break down and create a ticket...

  • 0 in reply to 

    Probably will not help, but it also will not hurt to restart rcnovell-famtd on Filr server.

    regs

  • 0

    Here's something I missed earlier though, could be nothing;

    As the local Admin on the Filr User page, when I select the Net Folders, the list shows "MODIFIED" 15-18 days ago, which is about when we performed the upgrade. Could be coincidence? The source OES NSS servers were definitely updated after this...

  • 0 in reply to 

    Restarted just now. I'll let it settle and try again. systemd Status shows the following;

    â—Ź novell-famtd.service - LSB: novell-famtd daemon provide CIFS / NCP file access from Filr Server.
         Loaded: loaded (/etc/init.d/novell-famtd; generated)
         Active: active (running) since Tue 2023-11-21 08:35:24 EST; 7s ago
           Docs: man:systemd-sysv-generator(8)
        Process: 13379 ExecStart=/etc/init.d/novell-famtd start (code=exited, status=0/SUCCESS)
          Tasks: 216
         CGroup: /system.slice/novell-famtd.service
                 └─ 13388 /opt/novell/filr/bin/famtd
    
    Nov 21 08:35:24 filr systemd[1]: Starting LSB: novell-famtd daemon provide CIFS / NCP file access from Filr Server....
    Nov 21 08:35:24 filr novell-famtd[13379]: Starting FAMT DAEMON ..done
    Nov 21 08:35:24 filr systemd[1]: Started LSB: novell-famtd daemon provide CIFS / NCP file access from Filr Server..
    Nov 21 08:35:24 filr famtd[13388]: WARNING:NeuServerInstance::Listener: FAMT Running with configured max threads= 200, max_queue_size=60 remote_conn=0.

  • 0 in reply to 

    No change. Thank you for the idea though!

  • 0

    opentext Case Number: 02743013

    I will report back with the solution when it makes sense to do so

  • 0 in reply to 

    You are not the only one. We are facing the same problem. Our Filr proxy user has the rights as described in the documentation but only the admin can see the network folders. As a workaround we are using the ldap admin user for network folder synchronisation/connection, with this User it works. We also have currently a ticket open.

  • Verified Answer

    +1

    I was missing that Net Folder Server, Filr specific "Rights" were empty. I added the "everyone" eDirectory/LDAP/Filr group and presto, everything works. No one here knows how every single one of our Net Folder Server entries had nothing there, but that's what happened. Adding the group back fixed everything instantly.