release-0.3.0

What's Changed

• Add support for saving tokens manually by @acoumb in #22
• Feature/api key support by @acoumb in #20
• Use authentication method for toggling visibility of revoke access ac… by @acoumb in #23
• OAuth2 Client Credentials implementation by @acoumb in #24
• Feature/manually add api key by @acoumb in #25
• Exchange access tokens implementation by @acoumb in #26
• Adds Meetup.com to example site by @warrenbuckley in #30
• OAuth1a authorization feature implementation by @acoumb in #28
• Refactors the IAuthorizedServiceCaller methods to use Attempt by @AndyButland in #32
• Added diagrams for flows. by @AndyButland in #33
• Updated docs by @acoumb in #29
• Add test services endpoints by @acoumb in #35

Breaking Changes

There are some breaking changes with this release. Most fit under the "unlikely to affect anyone" category, where we've made some changes to method names and interfaces that aren't typically something we expect users to replace.

There are a couple of important ones to note though.

Now we have introduced OAuth1 as well as OAuth2 support, we've amended the callback URLs you will need to configure with your service apps to:

For OAuth2: /umbraco/api/AuthorizedServiceResponse/HandleOAuth2IdentityResponse
For OAuth1: /umbraco/api/AuthorizedServiceResponse/HandleOAuth1IdentityResponse

The second key change is that we've refactored the IAuthorizedServiceCaller methods to return results wrapped in Umbraco's Attempt construct. We felt this was a valuable change to make, as it offers you more flexibility in handling failed responses, and avoids the necessity to use exceptions for "control of flow" in these situations.

New Contributors

• @warrenbuckley made their first contribution in #30

Full Changelog: release-0.2.0...release-0.3.0