NATS4 HTTPS Gateways

From TMM Wiki
Revision as of 16:12, 19 December 2008 by Trinidadr (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search
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

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 following line to your config.php file:

$config['GATEWAY_HTTPS'] = "https://mysecuredomain.com";

Make sure you include the "https://".