All geek questions in one place

Exchange Web Services, ASP.NET with Windows Auth, IIS 8.5 and Impersonation

IIS is setting up slowly and inexorably to allow access to Exchange web services from an ASP.NET website that uses Windows authentication. I literally found dozens of articles on how to install this, each of which seems to say something different, or describes a process that does not work when I duplicate it, presumably when there is some alleged knowledge on my part.

  • The application uses Windows authentication to authenticate the user.
  • The application sends emails using EWS so that the email address ends in the "sent items" of users.
  • Exchange is hosted on a separate server than the web server, so I assume that the “double jump” that I read about the problem occurs. I am not a system administrator, so I do not understand this.

Is there any clear way to set this up to work and then potentially fix the problem?

+4
source share
1 answer

Yes, from your description, this certainly looks like a two-hop problem. This is not trivial to fix, basically you need to configure delegation between the web server and the exchange server so that the web server can use the kerberos ticket issued when the user logs on to the web server.

, . , ( , ..) - . , , .

+1

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

More articles:


All Articles