Implemented OAuth support for Exchange Online and upgraded target framework to .net 4.8 #135
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
OAuth support for Exchange Online was added. Basic authentication can still be used by omitting the EWSOAuthSecret config element. For OAuth, an Exchange application with sufficient API permissions are required. The Client Secret for the Exchange application must be encrypted via DPAPI similar to the password file. Reference Config and Config Examples have been updated to and annotated with some descriptions.
Additionally, the Target Framework was bumped to .NET 4.8.0 in order to support Azure DevOps Server.
I could not verify that Basic Authentication still works, since my EWS environment doesn't allow Basic Auth anymore. Please check that the old method still works, but from the code alone nothing should have changed.
I've verified OAuth in my environment and it works like charm.