Difference between revisions of "NATS4 HTTPS Gateways"
From TMM Wiki
Jump to navigationJump to searchTmmStephen (talk | contribs) |
TMMStephenY2 (talk | contribs) |
||
| 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. | + | HTTPS is the usage of SSL certificates in order to provide encryption and secure identification in order to a secure a gateway. The ability to select how HTTPS is used on a per-tour basis has been added to [[NATS4]], and this option is available in the Sites Admin while editing a tour. |
| + | == Securing a Gateway With HTTPS == | ||
There are three ways to secure a [[ct#Gateway|gateway]] with HTTPS: | There are three ways to secure a [[ct#Gateway|gateway]] with HTTPS: | ||
| − | You can get a SSL certificate for each [[Link Domain|linkdomain]] and | + | *You can get a SSL certificate for each [[Link Domain|linkdomain]] and prefix the URLs that load these linkdomains with https: instead of http:. |
| − | prefix URLs that load | ||
| − | You can get a single certificate for your [[ct#Domain|domain]] and link to | + | *You can get a single SSL certificate for your [[ct#Domain|domain]] and link to your ''gateway_join.tpl'' template form. Note: this will send the surfer's data using HTTPS, but the surfer will load the form using HTTP -- this means surfers may think they aren't on a secure form, despite the SSL certificate that will encrypt their data. |
| − | ''gateway_join.tpl''. | ||
| − | but the surfer | ||
| − | they aren't on a secure form. | ||
| − | The last way set up HTTPS is to | + | *The last way set up HTTPS is to instruct all of the available gateways to use one secure domain. In order to do this, you will need to add the new domain to your list of NATS server aliases. This method has the added benefit of displaying a secure page while only requiring one certificate. You can set this 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 order to secure the domain. |
| − | |||
| − | This has the added benefit of displaying a secure page while only requiring one certificate. | ||
| − | |||
| − | 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. | 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 | + | == Controlling HTTPS usage == |
There are three different ways for a tour to get an HTTPS URL: GATEWAY_HTTPS, tour specific linkdomain or default tour linkdomain. | 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' | + | *GATEWAY_HTTPS will use the URL set in your configuration admin, under the 'surfer' option in the drop-down menu at the top of the page. To secure your link, you must enter the full URL including the https:// protocol. |
Example: | Example: | ||
<pre>https://mysecuredomain.com</pre> | <pre>https://mysecuredomain.com</pre> | ||
| Line 32: | Line 25: | ||
This allows you to use one SSL certificate across multiple sites. | 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 | + | *Tour specific linkdomain will use the HTTPS version of the linkdomain set in specific tours under the Sites Admin. |
*Default tour linkdomain will use the HTTPS version of the the linkdomain set in the default tour of a given site. | *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 | + | These last two options allow you to use an SSL certificate for each individual 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. | 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 | + | *''Everything'' will take the supplied HTTPS URL and use it for everything after the gateway join form. |
| − | *Gateway join page only will | + | *''Gateway join page only'' will take the supplied HTTPS URL and use it only for sending the data from the gateway join form. Pages other than the gateway join form will not be secure under this option. |
| − | *Gateway join page and return URLs will | + | *''Gateway join page and return URLs'' will take the supplied HTTPS URL and use it for sending data on the gateway join page and for any returned URLs sent back from the join page. |
Revision as of 14:49, 4 June 2010
HTTPS is the usage of SSL certificates in order to provide encryption and secure identification in order to a secure a gateway. The ability to select how HTTPS is used on a per-tour basis has been added to NATS4, and this option is available in the Sites Admin while editing a tour.
Securing a Gateway With HTTPS
There are three ways to secure a gateway with HTTPS:
- You can get a SSL certificate for each linkdomain and prefix the URLs that load these linkdomains with https: instead of http:.
- You can get a single SSL certificate for your domain and link to your gateway_join.tpl template form. Note: this will send the surfer's data using HTTPS, but the surfer will load the form using HTTP -- this means surfers may think they aren't on a secure form, despite the SSL certificate that will encrypt their data.
- The last way set up HTTPS is to instruct all of the available gateways to use one secure domain. In order to do this, you will need to add the new domain to your list of NATS server aliases. This method has the added benefit of displaying a secure page while only requiring one certificate. You can set this 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 order to secure the domain.
In the edit tour pages of your sites tour there is a "HTTPS use" feature allowing you to control how HTTPS is used.
Controlling 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' option in the drop-down menu at the top of the page. To secure your link, 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 specific tours under the Sites Admin.
- 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 individual 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 take the supplied HTTPS URL and use it for everything after the gateway join form.
- Gateway join page only will take the supplied HTTPS URL and use it only for sending the data from the gateway join form. Pages other than the gateway join form will not be secure under this option.
- Gateway join page and return URLs will take the supplied HTTPS URL and use it for sending data on the gateway join page and for any returned URLs sent back from the join page.
