release-10.0.1

What's Changed

• Ensured all configuration values are displayed in the settings section for the service. by @AndyButland in #50

Full Changelog: release-10.0.0...release-10.0.1

release-10.0.0

What's Changed

• No functional changes since the previous 0.4.1 release. Only update is to move to a non-zero major version number.
  • We'll release this version supporting Umbraco 10 through 13 as 10.0.0.
  • 14.0.0 will be released in future supporting Umbraco 14+.

Full Changelog: release-0.4.1...release-10.0.0

release-0.4.1

What's Changed

• Changed tokensize from 5000 to 4000 by @madsoulswe in #44

New Contributors

• @madsoulswe made their first contribution in #44

Full Changelog: release-0.4.0...release-0.4.1

release-0.4.0

What's Changed

• Refresh token with client credentials flow and use async for data access. by @AndyButland in #43

Breaking Changes

There are some breaking changes with this release related to the refactoring of the data access layer to be asynchronous. Some method names on public interfaces and now return Task or Task<T> responses.

Full Changelog: release-0.3.3...release-0.4.0

release-0.3.3

What's Changed

• Updated size of token columns for new installs and upgrades. by @AndyButland in #41

Full Changelog: release-0.3.2...release-0.3.3

release-0.3.2

What's Changed

• Update Umbraco reference interval by @acoumb in #39

Full Changelog: release-0.3.1...release-0.3.2

release-0.3.1

What's Changed

• Added the option of providing additional parameters in the header when making requests using API key authorization. by @AndyButland in #38

Full Changelog: release-0.3.0...release-0.3.1

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

release-0.2.0

What's Changed

• Install commands shouldn't be multiline by @abjerner in #12
• Ensure that when optional secret key for token encryption is not provided token is stored without encryption. by @AndyButland in #15
• Use PackageMigrationPlan and update version retrieval by @ronaldbarendse in #18
• Use named options for services configuration by @ronaldbarendse in #17
• Added package Id to package manifest. by @AndyButland in #19

Breaking Changes

In the update to 0.2.0 we've introduced a couple of small breaking changes:

• Configuration has now been modified to a dictionary structure, as can be seen in the readme. Documentation will be updated shortly after release.
• The default encryption implementation has been changed to be DataProtectionSecretEncryptor. Any existing stored tokens will need to be revoked and refreshed, or you can apply a code update to keep using the previous default AesSecretEncryptor implementation.

New Contributors

• @ronaldbarendse made their first contribution in #18

Full Changelog: release-0.1.2...release-0.2.0

release-0.1.2

What's Changed

• Include an Accept header by default to request JSON responses. by @AndyButland in #11

New Contributors

• @AndyButland made their first contribution in #11

Full Changelog: release-0.1.1...release-0.1.2