Hi,
We upgraded rt from 4.0.5 to 4.0.17 and rt command line client failed after the upgrading.
/opt/rt/bin/rt ls 18990
Query:id=18990
Strong encryption not available, switched off by externalauth=0
Password will be sent to rt.mydomin.com over SSL
Press CTRL-C now if you do not want to continue
Password:
rt: Server error: Can’t connect to rt.mydomin.com:443 (certificate verify failed) (500)
We are using self-signed certificate for the site. Please advise.
Below is .rtrc file
server https://rt.mydomain.com/
user test
Thanks,
Qiao
SC-ISAC, DSIT
(803)896-0597
qxin@cio.sc.gov
Hi,
We upgraded rt from 4.0.5 to 4.0.17 and rt command line client failed after the upgrading.
/opt/rt/bin/rt ls 18990
Query:id=18990
Strong encryption not available, switched off by externalauth=0
Password will be sent to rt.mydomin.com over SSL
Press CTRL-C now if you do not want to continue
Password:
rt: Server error: Can’t connect to rt.mydomin.com:443 (certificate verify failed) (500)
We are using self-signed certificate for the site. Please advise.
Presumably as part of this upgrade, you installed a newer LWP module
and are affected by this change:
https://metacpan.org/source/GAAS/libwww-perl-6.05/Changes#L120
RT itself documents how to work around this for the rt-mailgate
rt-mailgate - RT 4.0.25 Documentation - Best Practical (search
for ssl).
You may want to set the environment variable documented in the Changes
above, or teach your Linux system how to validate your self signed
certificate.
-kevin