-
Notifications
You must be signed in to change notification settings - Fork 74
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
Python-irodsclient needs different irods_authentication_scheme than iCommands in iRODS 4.3.0. #430
Comments
We are hoping to integrate the authentication plugin framework for PRC and other clients in the near future which would allow for using the new authentication scheme. @d-w-moore - What do you think about adding a shim for the |
When you say shim, are you saying to have the PRC accept |
Right, until we get the framework ported over. It could possibly trip up users and admins depending on how it's implemented, so it might be better to just prioritize porting the authentication framework. |
I think prioritizing the porting of the auth framework is the right way to go. I sense that making the PRC treat With that said, let's aim at starting the port next week. |
I'd have agreed to a shim as well, maybe , but I guess a port is cleaner? Yes, let's look into it next week. |
@d-w-moore - I think that the workaround to use the legacy auth plugins is working as of #461. The client-driven authentication flow will be implemented in #499. If agreed, please close when ready. |
Since iRODS 4.3.0., iCommands require the irods_authentication_scheme to be 'pam_password' instead of 'PAM' in the irods_environment.json if you are using PAM.
However, the Python-irodsclient still seems to require 'PAM', even if the server is 4.3.0.
This means that on a 4.3.0., users cannot use the same irods_environment.json for iCommands and the Python client.
This is inconvenient for two reasons:
Could some changes be made so that the Python-irodsclient also accepts 'pam_password'?
Slightly related to:
irods/irods#3164
irods/irods#6785
#370
The text was updated successfully, but these errors were encountered: