This
isn??™t disastrous when securing pages that are to be visited by your company personnel but would
certainly affect customer confidence if such a warning message shows up, for example, when
paying for an order.
If you configured your system using XAMPP, as described in Chapter 1, your Apache web
server is already configured with a certificate. If you set up Apache on your own, we recommend
CHAPTER 10 ?– CATALOG ADMINISTRATION: DEPARTMENTS AND CATEGORIES 271
you check out the article at http://www.sitepoint.com/article/securing-apache-2-server-ssl.
For test purposes, you can also get an SSL-enabled Apache version from http://www.devside.net/
web/server/free/download.
For a production scenario, you need to buy a trusted certificate through your web hosting
company, or, if you manage the web server yourself, obtain a SSL certificate from a known and
respected organization that specializes in web security, such as these:
??? VeriSign (http://www.verisign.com/)
??? Thawte (http://www.thawte.com/)
??? InstantSSL (http://www.instantssl.com/)
Web browsers have built-in root certificates from organizations such as these and are able
to authenticate the digital signature of SSL certificates supplied by them. This means that no
warning message will appear, and an SSL-secured connection will be available with aminimum
of fuss. For example, when loading such a URL in Opera, a little golden lock shows up next to
the address bar.
Pages:
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389