re #1034 Data encryption blog post

[kahboom]

Changes:

• Added a blog post on the encryption of data that apiman stores.
• Added myself as an author, and re-ordered list of names alphabetically (by first name).

Screenshots:

JIRA: https://issues.jboss.org/browse/APIMAN-1034

cc @EricWittmann @msavy - Sorry that this took forever, I wanted to make sure I was adding enough detail. A few comments:

1. Please check the accuracy of what I wrote, especially the comment about pre- and post-marshalling when storing in Elasticsearch toward the end. I was basing this off of my notes from a bootstrapping meeting and by looking at the code.
2. I didn't get too detailed for things like setting up the structure for a plugin, but did provide references. Maybe should have done that for generating an encrypted key as well.
3. I'd really like to add comments in today, if possible. It's a quick task that I think is pretty important. That's one of the reasons I mention "please leave a comment below" at the end of the post.
4. Last thing is, please don't merge this in yet as I've yet to commit the built files. This is just for you guys to read, review, and provide feedback (if you have the time!). It would be nice if this were done automatically in Travis CI / Jenkins.

Thanks!

[kahboom]

Blob is here, but obviously looks better when rendered locally (see screenshot).

[msavy]

s/Takeway/Takeaway/

[kahboom]

@EricWittmann @msavy - Made suggested changes, updated the date, and added Disqus commenting. See updated screenshot below.

It is desperately missing images, but I didn't think any would be helpful so decided to omit them completely. Once you guys are okay with it, let me know and I'll check in the built Jekyll files.

[EricWittmann]

This sentence isn't correct: "By default, the database storage is the H2 relational database, which uses Elasticsearch."

It should maybe be "By default, the API Manager uses a relational database for storage."

[kahboom]

Wow, I should probably start drinking coffee again. What I meant to say was, "By default, the database storage is the H2 relational database management system, which can be swapped out for Elasticsearch." But that's not necessarily correct anyway, since you're replacing JPA/Hibernate/H2 (or other RDBMS) with Elasticsearch. Also kind of irrelevant.