-
Notifications
You must be signed in to change notification settings - Fork 0
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
Upgrade for iRODS 4.3 #3
Comments
The lastest (pre-?) release of Davrods for iRODS 4.3 is 4.3.0_1.5.0. I'll have to see how well it works with iRODS 4.3.3 Since that release there doesn't seem to have been any work for iRODS 4.3 support. However, I noticed this comment for two weeks ago stating that they would be continuing this work "soon". I should maybe have checked on the status of Davrods dev sooner when I restarted my work on iRODS 4.3 upgrades.. Update: Then again rit-davrods has been updated for iRODS 4.3.2. Perhaps this will work. |
Got this to a point where the server is up and the module is loaded. No errors anywhere and auth request is successfully passed from Davrods to SODAR through iRODS. However, after a successful auth with SODAR via the custom PAM module, Davrods asks for authentication again and we are most definitely not authenticated. At the moment I can't completely discount this being due to some config error in my environment. I'll have to pin down the root cause. What exactly happens:
Davrods log:
iRODS log with
For a Things to note:
|
Log of a failed login with all log categories set to
|
iRODS support suggested this problem may be due to a PAM auth incompatibility between Davrods and iRODS 4.3 and it could not work to begin with. iRODS devs have opened an issue for dealing with this, see irods/irods#8016. However, Davrods should still be able to do the "legacy" style PAM auth. But how to make that work with 4.3.x? |
Workaround for PAM auth failing:
It would seem there is something wrong in the new version of the image I'm building. I need to still investigate that further, but at least we have a workaround. HOWEVER: with this setup, ticket URLs still fail with HTTP 500. For that, see #8. |
Alright soooo.. Turns out this is the same Next steps:
|
Hardcoded password length limit fixed. Still looking into logging problems and anonymous ticket access failing with |
Logging partially fixed. I can see davrods errors, but iRODS client errors are still not logged as they were in the previous Docker image build.. |
Logging fixed. The solution was to add the following lines under
Then, by setting |
Done except for #8 which I'll handle in another ticket, because it may not be actually related to this upgrade.. |
Together with bihealth/irods-docker#16 and bihealth/sodar-docker-compose#34, this needs to be updated as well.
Tasks
Upgrade to latest Davrods 4.3 releaseThere is no release, need to compile from sourcebuild.sh
andREADME.md
README.md
for new config etcThe text was updated successfully, but these errors were encountered: