Difference between revisions of "NATS4 HTTPS Gateways"

From TMM Wiki
Jump to navigationJump to search
m
 
Line 2: Line 2:
 
| show_billers_admin_section = true
 
| show_billers_admin_section = true
 
}}
 
}}
 +
HTTPS is the usage of SSL certificates to secure a gateway. We added the ability to select how HTTPS is used on a per-tour basis. This option is available in the Sites Admin while editing a tour.
  
 
There are three ways to secure a [[ct#Gateway|gateway]] with HTTPS:
 
There are three ways to secure a [[ct#Gateway|gateway]] with HTTPS:
Line 16: Line 17:
 
You need to add the new domain to your list of NATS server aliases.
 
You need to add the new domain to your list of NATS server aliases.
 
This has the added benefit of displaying a secure page while only requiring one certificate.  
 
This has the added benefit of displaying a secure page while only requiring one certificate.  
Set the option by adding the following line to your <tt>config.php</tt> file:
+
Set the option by adding the secure domain to the GATEWAY_HTTPS field in the configuration admin under the Surfer section.
 +
Make sure you include the "https://".
 +
 
 +
In the edit tour pages of your sites tour there is a "HTTPS use" feature allowing you to control how HTTPS is used.
 +
 
 +
HTTPS usage
 +
 
 +
There are three different ways for a tour to get an HTTPS URL: GATEWAY_HTTPS, tour specific linkdomain or default tour linkdomain.
 +
 
 +
*GATEWAY_HTTPS will use the URL set in your configuration admin, under the 'surfer' tab. You must enter the full URL including the https:// protocol.
 +
Example:
 +
<pre>https://mysecuredomain.com</pre>
 +
 
 +
This allows you to use one SSL certificate across multiple sites.
 +
 
 +
*Tour specific linkdomain will use the HTTPS version of the linkdomain set in the specific tour.
 +
 
 +
*Default tour linkdomain will use the HTTPS version of the the linkdomain set in the default tour of a given site.
 +
 
 +
These last two options allow you to use an SSL certificate for each linkdomain
 +
 
 +
There are also three different ways to start and stop using HTTPS during the sign up process: everything, gateway join page only, and gateway join page and return URLs.
  
<pre>
+
*Everything will use the supplied HTTPS URL and use it for everything after the gateway join form.
$config['GATEWAY_HTTPS'] = "https://mysecuredomain.com";
 
</pre>
 
  
Make sure you include the "https://".
+
*Gateway join page only will use the supplied HTTPS URL and use it for sending the data from the gateway join form.
 +
 
 +
*Gateway join page and return URLs will use the supplied HTTPS URL and use it for sending the data on the gateway join page and for any returned URLs sent back.

Revision as of 16:35, 24 December 2009

NATS 4
Members Admin
The Members Admin
View Member Details
Add Member
MySQL Auth
Mod Authn DB
Multisite Access
Member Logging
Member Password Retrieval
OpenID Connect
Mod Auth OpenIDC
ID Numbers
Billers Admin
The Billers Admin
Biller
Biller Fees
Taxes
NATS Cascades
Add Cascade
Cascade Weight
Autocascade
Hidden Cascades
Geo-Targeting Cascades
Post-Biller Templates
HTTPS Gateways
Timed Cascade Rules
Upgrade Plus
Token Plus
Gateway One Step Join
Extra Biller Fields
Send Information To Special Biller
Setting Rules
Cross Sell Supported Billers
Upsell Supported Billers
Packageplus Supported Billers
Tokenplus Supported Billers

HTTPS is the usage of SSL certificates to secure a gateway. We added the ability to select how HTTPS is used on a per-tour basis. This option is available in the Sites Admin while editing a tour.

There are three ways to secure a gateway with HTTPS:

You can get a SSL certificate for each linkdomain and prefix URLs that load this page with https: instead of http:.

You can get a single certificate for your domain and link to gateway_join.tpl. Note: this sends the surfer's data using HTTPS, but the surfer loads the form using HTTP -- this means surfers may think they aren't on a secure form.

The last way set up HTTPS is to tell all the gateways to use one secure domain. You need to add the new domain to your list of NATS server aliases. This has the added benefit of displaying a secure page while only requiring one certificate. Set the option by adding the secure domain to the GATEWAY_HTTPS field in the configuration admin under the Surfer section. Make sure you include the "https://".

In the edit tour pages of your sites tour there is a "HTTPS use" feature allowing you to control how HTTPS is used.

HTTPS usage

There are three different ways for a tour to get an HTTPS URL: GATEWAY_HTTPS, tour specific linkdomain or default tour linkdomain.

  • GATEWAY_HTTPS will use the URL set in your configuration admin, under the 'surfer' tab. You must enter the full URL including the https:// protocol.

Example:

https://mysecuredomain.com

This allows you to use one SSL certificate across multiple sites.

  • Tour specific linkdomain will use the HTTPS version of the linkdomain set in the specific tour.
  • Default tour linkdomain will use the HTTPS version of the the linkdomain set in the default tour of a given site.

These last two options allow you to use an SSL certificate for each linkdomain

There are also three different ways to start and stop using HTTPS during the sign up process: everything, gateway join page only, and gateway join page and return URLs.

  • Everything will use the supplied HTTPS URL and use it for everything after the gateway join form.
  • Gateway join page only will use the supplied HTTPS URL and use it for sending the data from the gateway join form.
  • Gateway join page and return URLs will use the supplied HTTPS URL and use it for sending the data on the gateway join page and for any returned URLs sent back.