Using Web to Lead forms with Sugar behind firewall

[cbarstow]

Hi,

I'm surprised this hasn't already been covered but I haven't been able to find a solution after extensive searching both here and in Wiki.

I need to get the output from a web to lead form on our public web server (hosted by 3rd party) into Sugar on a private server behind a firewall in our office without compromising security?

My thoughts on ways this might be achieved are:
Correct config of firewall to allow data through that doesn't compromise security
Use web to email form instead and extract data from email into Sugar using either:

Email to nominated email address or with specific subject sent to an email account set up in Sugar that then somehow generates a new lead, or

Internal email client (Outlook, etc) add on or independent app that can convert the email contents to format that can be submitted to the Lead Capture Script

Some other trick to getting the info through that I haven't thought of.

Any suggestions on how to achieve any of the above or any other solution would be much appreciated.

Thanks, Con.

Sugar Version: 5.2.0i (Build 5757) CE
Category: Web to lead
Operating System Win 2003 Server
PHP Version: 5.2.5
Database: 5.0.45
Web Server:Apache/2.0.59

[salesagility]

So, what's wrong with the SOAP API?

[cbarstow]

Hi Salesagility,

Um, not sure. Haven't got my teeth into the SOAP API yet. How would I use that to get output from a web form through a firewall to Sugar on a private subnet. Have a reasonably technical IT background so happy to learn.

Thanks, Con.

[johanw]

Another way is to just forward the POST data do a PHP script on the public server that uses the PHP Curl methods to send it right to sugar.

And then in the firewall add a rule that enables the public server to communicate to with the internal one.

[salesagility]

Hi Salesagility,

Um, not sure. Haven't got my teeth into the SOAP API yet. How would I use that to get output from a web form through a firewall to Sugar on a private subnet. Have a reasonably technical IT background so happy to learn.

Thanks, Con.

Goto Campaigns>Web to Lead form

create the webform for your remote server ... this then uses the SugarCRM SOAP API to insert the Lead Form data into SugarCRM ... no coding required

[johanw]

No... A web-to-lead form will not use SOAP without some coding. A web to lead form only posts the data to an sugar entrypoint (http://sugarserver/index.php?entryPo...bToLeadCapture).

[cbarstow]

Goto Campaigns>Web to Lead form

create the webform for your remote server ... this then uses the SugarCRM SOAP API to insert the Lead Form data into SugarCRM ... no coding required

Thanks. I have got the form working internally - i.e. from a webpage behind the firewall. The challenge I'm having is I need to get it to work through the firewall from our public web server hosted by a third party without compromising security.

If the only way to do this is by creating a firewall rule then what port, protocol, etc should I use to keep it secure.

[johanw]

Web-to-lead form uses port 80 and the http protocol to communicate with the sugar server.

Sugar SOAP also uses port 80 and the HTTP protocol to communicate with the server.

[jorgepelaez]

Hello to all, I'm new with Sugar and I need to use one form in another server.
I followed the instructions but when I add the html generated with Sugar in my other site and click on submit, nothing happens.


Checking the code the action shows 127.0.0.1:80. I'm not a programmer and I understand that this is a localhost address, right?

Am I missing something when creating the web form? Should I use an iframe to run the form?

Any advice is more than welcome.

[Danny K - Melonhead Multimedia]

I use the following method:

1. Web forms post leads to a simple mysql database on the public web server
2. A cron job (scheduler on M$Win) on my internal SugarCRM server uses wget to run a PHP SOAP script that consumes a PHP SOAP script on the public server to retrieve new leads.

There are several benefits to this approach:

• Security - pulling leads from inside eliminates the need for a pinhole in the firewall
• Reliabilty - if our Internet connection is disrupted, leads will continue to collect in the public db until the connection comes back online