Token exchange client. Oauth2 AS Metadata endpoint

What's Changed

• Rewrote Client/RP configuration handling by @rohe in #21
• Bumped version by @rohe in #22

Full Changelog: 1.1.1...1.2.0

Configuration refactoring

Client configuration refactoring

Client configuration refactoring

Separated out metadata handling such that extension services now can handler their own.
Clearer demarkation between what's metadata (that the client can tell the provider about) and what's not.

v1.0.12

Release notes

• initialize member variables and remove magic kids @jschlyter (#16)
• Updated _unwrap_identity. @rohe (#15)
• Encountering cookie or session ID error at the authorization endpoint will result in the user having to do a new authentication.
• Allow the usage of FernetEncrypter in the CookieHandler.

v1.0.11

Release notes

• updated the _unwrap_identity method

v1.0.10

Release notes

• The fact that an endpoint knew in advance (through configuration and the applicable standards) was not used. Not it is !

v1.0.9

Release notes

• chore: README structure and common sections @peppelinux (#11)
• fix: [README] CI badge @peppelinux (#12)
• fix: CI with a matching master branch @peppelinux (#10)
• Verifying client configuration

v1.0.8

Release notes

• To make sure I got everything that should have been in 1.0.7

v1.0.7

Release notes

• use default random binary key for FernetEncrypter @jschlyter (#8)
• changed to use special crypto configuration to get around the unit test speed problem.
• Completed the move from Crypt to FernetEncrypter.

v1.0.6

Release notes

• Refectored handling of client_authn_methods on the client side to be more like what it is on the server side.
• Fixed some problems with single logout