irods_testbench_training_python_bash/documentation/2) iRODS cyberduck.md

iRODS cyberduck

iRODS cyberduck

This is really convienient but doesnt offer control over metadata, very useful for testing rulesets and iROD client scripts.

Irods server should have an SSL certificate and all clients validate either via public CA or local CA with updated CA certs. To allow cyberduck to use not validate the irods cert as on our test virtual server (or something akin to this - maybe its even client auth?) a server side setting can be changed to accomodate an HTTP connection instead of only the default HTTPS connection:

nano -cw /etc/irods/core.re

#acPreConnect(*OUT) { *OUT="CS_NEG_DONT_CARE"; }
acPreConnect(*OUT) { *OUT="CS_NEG_REFUSE"; }

Cyberduck needs a profile in C:\Program Files\Cyberduck\profiles with minimally the Zone/Resource configured.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
    <dict>
        <key>Protocol</key>
        <string>irods</string>
        <key>Vendor</key>
        <string>iRODS</string>
        <key>Description</key>
        <string>iRODS Cyberduck Bookmark</string>
        <key>Hostname Configurable</key>
        <true/>
        <key>Port Configurable</key>
        <true/>
        <key>Default Hostname</key>
        <string>192.168.150.56</string>
        <key>Region</key>
        <string>OCF:OCFs3Resc</string>
        <key>Default Port</key>
        <string>1247</string>
        <key>Username rods</key>
        <string>iRODS username</string>
        <key>Password password</key>
        <string>iRODS password</string>
    </dict>
</plist>