[Cyberduck-trac] [Cyberduck] #9913: iRODS support is broken in versions of Cyberduck since 5.2.3

[Cyberduck]

#9913: iRODS support is broken in versions of Cyberduck since 5.2.3
--------------------------+--------------------
 Reporter:  danielhanlon  |         Owner:
     Type:  defect        |        Status:  new
 Priority:  normal        |     Milestone:
Component:  irods         |       Version:  5.4
 Severity:  normal        |    Resolution:
 Keywords:                |  Architecture:
 Platform:                |
--------------------------+--------------------
Description changed by dkocher:

Old description:

> We run a large storage facility for academic researchers based on the
> iRODS middleware and have been recommending Cyberduck to users who prefer
> a GUI. In recent versions of Cyberduck the support for iRODS has broken
> and it is not possible to authenticate. The version we are therefore
> asking users to stay with is 5.2. All newer versions that I have tested
> fail to connect.
>
> The issue has been discussed on the iRODS-chat mailing list at
> https://groups.google.com/forum/#!searchin/iROD-
> Chat/cyberduck%7Csort:relevance/irod-chat/F1HaH4BGEcs/aGQgRsz7AQAJ
>
> I'm replicating it here:
>
> "We're noticing problems with the current version of Cyberduck and PAM
> authentication. Version 5.2 was fine but after upgrading to 5.3 PAM
> logins fail with:
>
> Connection failed
> Error code received from iRODS: -319000
>
> Logging in with a non-PAM account still works
>
> Looking through the irods server logs there seems to have been a change:
>
> The older, working version simply has: (username replaced with xxxxxxx)
>
> Jan 19 14:53:14 pid:13907 NOTICE: Agent process 38176 started for
> puser=xxxxxxx and cuser=xxxxxxx from 144.82.115.64
>
> whereas the newer, failing version has:
>
> Jan 19 14:54:58 pid:13907 NOTICE: Agent process 38245 started for
> puser=xxxxxxx and cuser=xxxxxxx from 144.82.8.64
> Jan 19 14:54:59 pid:13907 NOTICE: Agent process 38247 started for
> puser=xxxxxxx and cuser=xxxxxxx from 144.82.8.64
> Jan 19 14:54:59 pid:38247 NOTICE: readAndProcClientMsg: received
> disconnect msg from client
> Jan 19 14:54:59 pid:38247 NOTICE: Agent exiting with status = 0
> Jan 19 14:54:59 pid:13907 NOTICE: Agent process 38248 started for
> puser=xxxxxxx and cuser=PAM:xxxxxxx from 144.82.8.64
> Jan 19 14:54:59 pid:13907 NOTICE: Agent process 38247 exited with status
> 0
> Jan 19 14:54:59 pid:13907 NOTICE: Agent process 38250 started for
> puser=PAM:xxxxxxx and cuser=PAM:xxxxxxx from 144.82.8.64
> Jan 19 14:54:59 pid:38250 NOTICE: rsAuthCheck: chlCheckAuth status =
> -319000
>
> I've tested a few versions now on Windows (7,8 and 10) and macOS and it
> seems that it's been broken on all of them since 5.3.0.
>
> My guess of the culprit change from the log is:
>
> [Feature] Use multiple connections in browser for parallel background
> task executions
>
> I hope it's possible to re-enable full iRODS support as Cyberduck has
> been very useful to a lot of researchers, especially those who have to
> transfer large (of the order of 1TB) files where iRODS' parallel transfer
> support is useful.
>
> Many thanks,
>
> Daniel.

New description:

 We run a large storage facility for academic researchers based on the
 iRODS middleware and have been recommending Cyberduck to users who prefer
 a GUI. In recent versions of Cyberduck the support for iRODS has broken
 and it is not possible to authenticate. The version we are therefore
 asking users to stay with is 5.2. All newer versions that I have tested
 fail to connect.

 The issue has been discussed on the iRODS-chat mailing list at
 https://groups.google.com/forum/#!searchin/iROD-
 Chat/cyberduck%7Csort:relevance/irod-chat/F1HaH4BGEcs/aGQgRsz7AQAJ

 I'm replicating it here:

 "We're noticing problems with the current version of Cyberduck and PAM
 authentication. Version 5.2 was fine but after upgrading to 5.3 PAM logins
 fail with:


 {{{
 Connection failed
 Error code received from iRODS: -319000

 }}}

 Logging in with a non-PAM account still works

 Looking through the irods server logs there seems to have been a change:

 The older, working version simply has: (username replaced with xxxxxxx)


 {{{
 Jan 19 14:53:14 pid:13907 NOTICE: Agent process 38176 started for
 puser=xxxxxxx and cuser=xxxxxxx from 144.82.115.64

 }}}

 whereas the newer, failing version has:


 {{{
 Jan 19 14:54:58 pid:13907 NOTICE: Agent process 38245 started for
 puser=xxxxxxx and cuser=xxxxxxx from 144.82.8.64
 Jan 19 14:54:59 pid:13907 NOTICE: Agent process 38247 started for
 puser=xxxxxxx and cuser=xxxxxxx from 144.82.8.64
 Jan 19 14:54:59 pid:38247 NOTICE: readAndProcClientMsg: received
 disconnect msg from client
 Jan 19 14:54:59 pid:38247 NOTICE: Agent exiting with status = 0
 Jan 19 14:54:59 pid:13907 NOTICE: Agent process 38248 started for
 puser=xxxxxxx and cuser=PAM:xxxxxxx from 144.82.8.64
 Jan 19 14:54:59 pid:13907 NOTICE: Agent process 38247 exited with status 0
 Jan 19 14:54:59 pid:13907 NOTICE: Agent process 38250 started for
 puser=PAM:xxxxxxx and cuser=PAM:xxxxxxx from 144.82.8.64
 Jan 19 14:54:59 pid:38250 NOTICE: rsAuthCheck: chlCheckAuth status =
 -319000

 }}}

 I've tested a few versions now on Windows (7,8 and 10) and macOS and it
 seems that it's been broken on all of them since 5.3.0.

 My guess of the culprit change from the log is:

  * [Feature] Use multiple connections in browser for parallel background
 task executions

 I hope it's possible to re-enable full iRODS support as Cyberduck has been
 very useful to a lot of researchers, especially those who have to transfer
 large (of the order of 1TB) files where iRODS' parallel transfer support
 is useful.

 Many thanks,

 Daniel.

--

--
Ticket URL: <https://trac.cyberduck.io/ticket/9913#comment:2>
Cyberduck <https://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows