-
Notifications
You must be signed in to change notification settings - Fork 36
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
Permissions of collection object #352
Comments
That looks like a bug. What version of iRODS are you running Metalnx against? |
iRODS v4.3.0 and metalnx v2.6.1 |
I bet this is because metalnx hasn't yet learned about the change from 'read object' to 'read_object' in 4.3.0. And probably also 'modify object' -> 'modify_object'. |
@trel That makes sense. In fact my iRODS server logs report
upon initiating a connection. PS: how does
|
I'm not sure, but my guess is that there may be background processes running within the Metalnx server that require admin level privileges. Some operations offered by Metalnx may also require temporary escalation of privileges as well. NFSRODS does a similar thing, so it isn't uncommon to find admin credentials in iRODS software. |
I am just wondering..clearly many admin ops can also be performed if an admin logs in via the web interface.. |
yes, metalnx caches many things in its own database and does so via admin credentials. there is also a background 'jobs' process - you can find it in the metalnx.properties file - also requires rodsadmin. we are planning to remove the database (#214) as part of 3.0.0 - and therefore may metalnx a pure client, no admin requirements. |
I have the same issue with the permissions displayed in metalnx not matching the icommands Any lead on a solution ? Thanks in advance :) I am using iRODS 4.3.1, and I don't know my metalnx version (how/where can I get it ?). |
We're currently preparing for our annual UGM and working on the release of iRODS 4.3.2. At the very least, there won't be a fix for this until after 4.3.2 is released. |
Ok thank you ! |
Hello, I am testing the latest version of
metalnx
and I get a permissions discrepancy between what I see on the server viaicommands
and what it is displayed bymetalnx
. For instanceand
Is this the desired behavior? Thanks in advance.
The text was updated successfully, but these errors were encountered: