-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
federated users cannot access iRODS via NFSRODS #171
Comments
I see an invalid client user error. Q. Are you trying to access a federated zone via NFSRODS? |
Q. Are you trying to access a federated zone via NFSRODS? I think so the machine is part of the humgen zone and I am accessing something in the SANGER zone Q. What rodsadmin user is NFSRODS configured to use?
Q. What Unix username are you attempting to access the mount point as? jb23 Q. Is /etc/hosts being used to resolve Unix usernames to iRODS usernames? I am not sure I understand the question /etc/hosts and Unix usernames -> iRODS usernames ? We are using DNS for hostname lookup, our users are in LDAP via sssd |
Sorry, I meant /etc/passwd instead of /etc/hosts. You provided what I wanted to know though :-). I'm wondering if the problem has to do with the username seen by NFSRODS and iRODS. We'll look into reproducing this issue. What OS and version of iRODS are you running? |
Sorry stupid architecture question, the docker container with nfsrods is a iRODS client talking to a local server ?
|
Yes. It translates NFS operations into iRODS API calls. |
Any thoughts ? |
Nothing yet. We'll update the issue once we know more. What version of NFSRODS are you using? |
We are using 2.1.0 |
Please confirm the following. I want to make sure I've captured the correct info.
I just noticed the default resource in your NFSRODS config is set to And can you explain these lines from your first post? jb23@farm5-humgen-nfsrods:~$ cd /mnt/humgen/home/j
****** jc18#Sanger1/ *****
jb23#Sanger1/ ***** |
The default resource is set to demoResc, neither the hugen or the Sanger1 zone are testing enviroments. I just deleted the output that may have been private. |
No, he is accessing |
In case its not clear, the only account in that zone for jb23 was |
Based on what has been said, the behavior you're seeing is expected. NFSRODS is implemented to present a single collection within a zone. It assumes that every user accessing the mount point is a member of the zone it is configured to handle. This explains why you received an Notice line 40 below. NFSRODS instantiates all iRODS users using the zone defined in the config file. irods_client_nfsrods/irods-vfs-impl/src/main/java/org/irods/nfsrods/vfs/IRODSUser.java Lines 22 to 44 in 6f316fc
Is the behavior you're seeing surprising? What do you feel NFSRODS should do in this case? |
I don't think NFSRODS can do anything about this scenario. Ideas welcome. |
On the client some access does work for example ls /home works
The nfs server config is
The text was updated successfully, but these errors were encountered: