Hi Xavier,
This error is not coming from the Workbench itself, but rather from
PHP when the soapclient is trying to make an SSL connection to
Salesforce (not the SSL connection to
https://localhost). From
googling this error, there are others that are having this issue with
other applications that use the soapclient, but this posting from
http://webponce.com/rants/2008/04/https-support-for-soap-in-php5-under-windows/
seems to be the most straightforward:
If you’re seeing error messages about missing https wrappers when
trying to use SOAP (”Unable to find the wrapper “https” - did you
forget to enable it when you configured PHP?” or “[HTTP] SSL support
is not available in this build”), you haven’t installed the SSL
libraries to support secure transactions.
1. Uncomment
extension=php_soap.dll
in your php.ini
2. Uncomment
extension=php_openssl.dll
in your php.ini
3. Copy
ssleay32.dll
and
libeay32.dll
to your windows system32 directory
4. Reboot apache, et voila!
If it is still not working, you could try a different LAMP/WAMP/MAMP
package that has SSL already enabled for the soapclient. A poster at
http://community.salesforce.com/sforce/board/message?board.id=PerlDevelopment&message.id=1210
had luck with the full XAMPP (
http://sourceforge.net/projects/xampp/),
not XAMPPlite.
If you still can't get it working, please send me you phpinfo() page
(as explained in installation) and php.ini and I can take a look.
Also, if you just want to try to Workbench without SSL to Salesforce,
you can go Advanced login and change the Server Url from HTTPS to
HTTP, and make sure that you have "Require secure connections (https)"
in Saleforce disabled under Setup | Security Controls | Session
Settings.
Hope this helps. Let me know if you have any other questions.
-Ryan
On Mar 3, 7:46 pm, Xavier <
yzav...@gmail.com> wrote:
> Hi, I wish to try out Workbench but I am getting the error "SSL
> support is not available in this build" everytime I try to login into
> workbench.
>
> I am running workbench2.2.15_2009-02-15 on XAMPPLite, and the SSL
> seems to have already enabled (I am able to login tohttps://localhost).