Message from <S.Popovic-Ovcina@iaea.org> via eLink<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
Would anyone be in a position to confirm whether the following (from LAPI documentation) is still (version 9.5 SP1) valid:
==============================================Secure TunnellingLAPI applications that do not implement LAPI security functions cannot ensure the confidentiality of data passed over the Internet or any unsecured network. By default, data exchanged between LAPI client applications and Livelink servers is passed in unencrypted messages (plaintext). If someone intercepts a plaintext message, they may be able to view its contents. Since most LAPI functions include sensitive data, such as a user ID and password (and may include a document added to or retrieved from Livelink), it is important to protect any LAPI transmission made on an unsecured network.Note: Secure tunnelling is supported for LAPI applications written in C++, Java, and Visual Basic. Secure tunnelling is not supported for .NET languages or with proxy server tunnelling.LAPI secure tunnelling requires Livelink Secure Connect. You must separately purchase and install Livelink Secure Connect before you can implement secure communications from your LAPI applications. Livelink Secure Connect includes RSA BSAFE cryptographic and security protocol software from RSA Security, Inc. The LAPI functions that support security allow you to protect the confidentiality of a LAPI application by converting plaintext messages to ciphertext, a form of secure, encrypted data. The data is virtually impossible to decipher if intercepted but is easily converted to plaintext by the application that is intended to receive the data. ==========================================If yes, is there any way we can use LAPI with https (SSL) in our VB.NET application?Thank you in advance,Sandra
This email message is intended only for the use of the named recipient.Information contained in this email message and its attachments may beprivileged, confidential and protected from disclosure. If you are not theintended recipient, please do not read, copy, use or disclose thiscommunication to others. Also please notify the sender by replying to thismessage and then delete it from your system.
