1 of 1 people found this helpful
Because the connection to the appserver is encrypted and the 1st time you connect you need to put it in your local keystore.
Echo y | blcred cert –add –host HOST:PORT –protocol tls
Should do it.
Thanks Bill -
I can't pass the "echo yes|" into my remote call. But that's not a blade issue, that's a quoting issue or a shortcoming of the way I'm doing the remote call.
If I actually create a script on the appserver that has that syntax, and then remotely call that script, it works for me. Given the extra hoops that involves jumping through, I'd hoped to avoid doing it that way.
I still don't get why being logged in to the app server somehow automatically makes its certificate acceptible to remote sessions. I'm not even logged in to the console...
Using blcred and the blcli is like using the GUI. the connection needs to be encrypted. You are connecting a client utility (blcred, blcli) to the appserver. no matter where that is initiated from, it will be encrypted.