All geek questions in one place

Authentication for Exchange Web Services with no username and password and no administrator

Here is the script

  • Third-party application with the back. The client uses the application.
  • The back should access user exchange information, presumably through EWS
  • The back end works in our data center / cloud, not in clients.
  • Local Administrator May Not Be Required
  • Want to avoid storing username and password at our end.
  • Want to support both Office365 and locally.

I believe this is currently not possible, but I need to check:

  • Impersonation would be a great way, but requires an administrator
  • Token-based authentication is not used for this. This mail application is used for SSO for the backend, not for the backend for accessing Exchange.
  • OAUTH would be ideal, but is a) only currently for Office365; b) requires that the back end be hosted by Azure; c) The Azure installation should be related to the Office365 installation and intended only for the local administrator.

Is my analysis correct? Any options I missed?

+4
source share
2 answers

So, to add to this basically the correct answer from Jason:

  • using pure relaxation, you only need to create a "multi-user" application, and users can independently agree.
  • OAuth EWS - " ". , ( , EWS ).
0

. OAuth Office 365, . , OAuth back-end Azure. Azure , Azure. EWS, OAuth , EWS , , , .

REST API, , , . , ( , API REST , ), .

+2

Source: https://habr.com/ru/post/1545894/

More articles:


All Articles