*: don't let generated comment become package comment

Load trustedPeers in no DB mode, add x-client to example app

* add trustedPeers to a client in client.json.sample
* add optional cross client auth to example web app
* login page is now templated

#400 Add connector id to the registration error message

Right now it is not clear what connector is failing. It will be easier to debug with more specific error message.

Related to #400.

Checking that trusted peers exist means that you have to create clients
in a certain order, or else create all the clients, then update trusted
peers. Either way, not a great experience during setup.

The downside, of course, is that you lose validation of peer
IDs.

The Client object on its own doesn't fully express everything about a
single client, and so when loading clients from a static configuration
it's not enough to just (de)serialize clients.

To that end, LoadableClient contains the full representation of a client
and associated entities.

Cross client work 

also, RevokeClient -> RevokeClient for consistency.

Trusted Peers are clients that are authorized to mint tokens
for another client.

Various client api tweaks

Replaced by ClientRepoFromClients, which makes more sense IMO. Also, it
was doing the wrong thing: it was ignoring the client_id and client_secret
passed into it as far as I can tell.

Use the test fixture setup stuff in testutil instead.

Use the test fixture setup stuff in testutil instead.

Also tests that it's being loaded properly (which is not the case in
NewClientManagerFromClients, which will be removed in subsequent commit)

*: Update Go versions used for Travis tests and test tip

Added TLS support to the example application

connector_ldap: Implement connection pooling for LDAP connections

Fixes #309

a little easier to read this way IMO.

Set and list connectors from admin API

closes #360

* Create releases.md

* (SQUASH) make note about keys

vendor: update go-oidc to latest