Closed stsnel closed 2 months ago
Can you show me what values do you have for following fields in ~/.irods/irods_environment.json?
irods_client_server_negotiation
should be set to request_server_negotiation
and irods_client_server_policy
should be set to CS_NEG_REQUIRE
or CS_NEG_DONT_CARE
.
Can you check if the new release v0.10.3 fixes the issue? https://github.com/cyverse/gocommands/releases/tag/v0.10.3
Thank you for the fix! The issue no longer occurs with v0.10.3 in our development environment.
For the record, our irods_client_server_negotiation
and irods_client_server_policy
settings are:
irods@combined:~$ grep irods_client .irods/irods_environment.json
"irods_client_server_negotiation": "request_server_negotiation",
"irods_client_server_policy": "CS_NEG_REQUIRE",
Thank you for the check! Glad it worked!
Good day,
I was testing GoCommands version v0.10.2 with our Yoda development environment, and would like to report a possible regression. It seems that v0.10.2 fails with authentication errors for commands that work as expected with older GoCommands versions, as well as iCommands. The rodsLog output indicates that the problem may be related to SSL/TLS settings.
Example output for iCommands, older GoCommands versions, and v0.10.2:
Debug output for GoCommands v0.10.2:
rodsLog output when trying to use v0.10.2:
I'm running GoCommands from the irods service account on the server, with native authentication. The server is running iRODS 4.2.12 and has
irods_client_server_policy
set toCS_NEG_REQUIRE
.