Secure Communication - Summary

In this article, I emphasized the importance of encrypting data as it travels between a mobile device and a server. I also demonstrated how to temporarily support self-signed certificates on a server (PHP, J2EE) and on a mobile device (iOS, and Android).

At this point, I haven't retrieved (or sent) anything that's sensitive. That will change in the next article. However, even if there's nothing sensitive, I personally consider it a good practice to start with secure communication. (For emphasis, I'll repeat my mantra: Things that start off small tend to end up getting large, so it's best to practice good design from the beginning.)

In the next article, I'll revisit Facebook authentication, and demonstrate how to share this information securely with a server.

Helpful Links (Thank you!)

The following links were particularly helpful for me to better understand this topic:

How to create a self-signed certificate:

How To Configure Tomcat To Support SSL Or Https:

Stack Overflow - didReceiveAuthenticationChallenge not getting called:

Stack Overflow - How can i migrate SSL from Tomcat to Apache HTTPD?

How to configure HTTPS on Apache 2:

Apache SSL on Mac OSX Lion 10.7