Closed Venustiano closed 5 months ago
Can you give me more details to reproduce the issue? What commands did you use after ./gocmd init
?
Also, can you check if the session file ~/.irods/irods_environment.json.<ppid number>
has different authentication scheme?
I suppose you have reproduced the issue, but just in case,
After running ./gocmd init
the go commands run fine ls
, get
, put
, etc.. After a while gocommands
is misconfigured and cannot access iRODS anymore as described above.
There is no ~/.irods/irods_environment.json.<ppid number>
session file created.
Pushed a commit 6543a67eee3a053500caaa34eacab53032024d57 that adds a new flag --ttl
to control PAM password TTL time.
With PAM authentication, iRODS server invalidates the PAM token (temporary password) after 1 hour by default. To increase you need to specify TTL when running gocmd init
.
A new release including the commit will be released in few days.
The new version is here. https://github.com/cyverse/gocommands/releases/tag/v0.9.0
I am using 'gocommands' v0.8.5 for MacOS M2. My config file is using PAM authentication
After running
./gocmd init
the immediate interaction withiRODS
is fine. However, after a couple of hours simple commands such as./gocmd ls
or even./gocmd init
result in the following errorFor some reason
gocommands
is usingnative
authentication but it is supposed to usePAM
. The only way I have found to gain access again into iRODS is by removing the.irodsA
file and running./gocmd init
again.