Adding support to nickname on --server option
Merge pull request #613 from fabianofranz/master

Merged by openshift-bot
Improvements to inline help
Merge pull request #615 from fabianofranz/master

Merged by openshift-bot
Automatic commit of package [rhc] release [1.27.1-1].
Bug 1115386 - remove stray space from cloned app environment variables
Merge pull request #616 from domcleal/1115386-clone-env-space

Merged by openshift-bot
Automatic commit of package [rhc] release [1.27.2-1].
Bug 1116709 - Modified the domain rename message to inform about applications that will be created
Bug 1117466 - should not reuse SSL certs from different server configs
Merge pull request #622 from fabianofranz/bugs/1117466

Merged by openshift-bot
Merge pull request #620 from jcantrill/1116709_unclear_notificatio_message

Merged by openshift-bot
x509 auth

This adds x509 as the second "core auth" mechanism.  That means you can have
either Basic or x509.  Both will still work with tokenized authentication.
Always attempt to use Tokens if they are configured

Previously:

1) If rhc has a token it will use it
2) If doesn't think it can get one it will use 'core auth'.  Today it's
  only Basic Auth
3) If it falls through it will issue a bogus request that has no auth
mechanism and rely on a 401 to trigger the token retry logic.

During the first request @can_get_token == false was always false since it's
not set until after the API has been fetched.

Now:

If tokens are configured they will attempted.  If one doesn't exist the Bearer
header value will be empty and trigger the 401 logic as before.
'rhc server' support for x509

This allows servers to optionally suport x509 authentication.  Previously there
was no support for keys.