Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
rdms:access:linux:lwpfuse [2023/05/02 14:57]
giulio [General Information] 		rdms:access:linux:lwpfuse [2024/04/25 16:15] (current)
jelte added ref to lowercase
Line 1: Line 1:
-====== iRDOS Fuse lite (irodsfs) ======+====== iRODS Fuse lite (irodsfs) ======
 ===== General Information ===== ===== General Information =====
  
-While you can access your RDMS collections by connecting to the RDMS remotely when using iCommands, you can also create a space on your machine where you can access the RDMS directly as if it were part of your local directory hierarchy. This action of making a remote directory available on your local system is called "mounting" in technical terms.+While you can access your RDMS collections by connecting to the RDMS remotely when using ''iCommands'', you can also create a space on your machine where you can access the RDMS directly as if it were part of your local directory hierarchy. This action of making a remote directory available on your local system is called "mounting" in technical terms.
  
 Linux users are able to mount iRODS collections and data objects (i.e. the iRODS version of directories and files) in their local directory hierarchy by using ''irodsfs'', a FUSE implementation of the iRODS client that you can download here: https://github.com/cyverse/irodsfs.  Linux users are able to mount iRODS collections and data objects (i.e. the iRODS version of directories and files) in their local directory hierarchy by using ''irodsfs'', a FUSE implementation of the iRODS client that you can download here: https://github.com/cyverse/irodsfs. 
Line 46: Line 46:
 </code> </code>
  
-Open the created ''config.yaml'' file and paste the following content in it, then save the file:+Open the created ''config.yaml'' file and paste the following content in it, then save the file (take notes below into account):
  
 <code> <code>
-host: rdms-prod-icat.data.rug.nl+host: store.data.rug.nl
 port: 1247 port: 1247
 proxy_user: <username>@rug.nl proxy_user: <username>@rug.nl
Line 57: Line 57:
  
 auth_scheme: "pam"  auth_scheme: "pam" 
-ssl_ca_cert_file: "/etc/ssl/certs/ca-bundle.crt"+ssl_ca_cert_file: "/etc/ssl/certs/ca-certificates.crt"
 ssl_encryption_key_size: 32 ssl_encryption_key_size: 32
 ssl_encryption_algorithm: "AES-256-CBC" ssl_encryption_algorithm: "AES-256-CBC"
Line 68: Line 68:
     resource_type: dir     resource_type: dir
 </code> </code>
-**Attention!** +**Notes:** 
-In  ''irodsfs'' versions prior to v0.8.3 the configuration file used ''autscheme'' instead of ''auth_scheme''. Please check the version of ''irodsfs'' you are using and keep this in mind when using configuration file in the example above! +  * In  ''irodsfs'' versions prior to v0.8.3 the configuration file used ''autscheme'' instead of ''auth_scheme''. Please check the version of ''irodsfs'' you are using and keep this in mind when using configuration file in the example above!  
 +  * Depending on your Linux distribution (e.g. CentOS), you might need to adjust ''/etc/ssl/certs/ca-certificates.crt'' to ''/etc/ssl/certs/ca-bundle.crt'' or equivalent.  
 +  * Keep in mind that your UG mail addressed needs to be specified in lowercase!
  
 Another important aspect is that you take care to verify that the correct username is specified in the configuration file. To access the RDMS, you need to input your RUG email as your username. Another important aspect is that you take care to verify that the correct username is specified in the configuration file. To access the RDMS, you need to input your RUG email as your username.
Line 111: Line 113:
  
 <code> <code>
-host: rdms-prod-icat.data.rug.nl+host: store.data.rug.nl
 port: 1247 port: 1247
 proxy_user: <username>@rug.nl proxy_user: <username>@rug.nl
Line 119: Line 121:
  
 authscheme: "pam"  authscheme: "pam" 
-ssl_ca_cert_file: "/etc/ssl/certs/ca-bundle.crt"+ssl_ca_cert_file: "/etc/ssl/certs/ca-certificates.crt"
 sslencryption_key_size: 32 sslencryption_key_size: 32
 ssl_encryption_algorithm: "AES-256-CBC" ssl_encryption_algorithm: "AES-256-CBC"