There have been some occasional requests for exposing NSS via NFSv4 protocol. If this is of interest to you please, add a comment with the use case and up vote it.
by: Madhan P. | over a year ago | NSS
Micro Focus Enhancement Requests Portal is moving. We are migrating the IDEAS from this site to the New Idea Exchange on May 6th. For more information on the new Idea Exchange please visit the Community FAQs.
Votes
25
NSS support for NFSv4
by: Madhan P. | over a year ago | NSS
Comments
this would be quite useful for e. g. backing up groupwise with gwava reload!
You can make one really central homedirectory for a user - irrelevant which kind of OS he use (Windows/NCP; Windows/CIFS; Linux/NFSv4; MacOS/CIFS).
It is accessable by the favorite access protocol of the OS.
Exporting NSS volumes via NFSv4 is required to allow clients to benefit from lock-blocking, plus the ability to present each export as appearing to be a subdirectory of the pseudo-fs.
I'll just "bump" and join the choir by agreeing with Gerd's comment: we need to expose the same home directory for all users. It should be irrelevant which platform they log on from - Windows, Linux or MacOS.
And on a side note: if this "gateway function" could be combined with Cloud Integration in OES, but instead expose private cloud storage (i.e. Ceph/SES) as NSS volumes, it would be brilliant!
Last time I had a look at Linux Desktop both KDE and Gnome refused to work without the right to define symbolic links in the $HOME folder. So while the concept of a common home folder for all OS is tempting OES might be not the right platform to do this. Or can I set symbolic links via NFS? It will not work on NSS through CIFS or NCP.
Symbolic links should work with NFS. I've used NFS mounts for home directories before and it's always worked well.
Thank you very much for the information. As there is no support yet for NFSv4 we never tested NFS for OES for obvious security reasons.