- Configure the server to require encryption from the clients - use a specific tcp port and handle the encryption between the two endpoints (e.g., stunnel) - create an ipsec tunnel between the two hosts
Axton Grams On 10/19/07, maggie2007 <[EMAIL PROTECTED]> wrote: > Usually, I login to > remedyServer.Login(ServerName, UserId, Password, "", ServerPort); > so the username and password will be clear/plaintext in tcp/ip packet. > Anybody knows how to implement SSL with Remedy API call (so the username and > password will be encrypted)? > -- > View this message in context: > http://www.nabble.com/Remedy-API-support-SSL--tf4654736.html#a13299418 > Sent from the ARS (Action Request System) mailing list archive at Nabble.com. > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the > Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
