Exchange Web Services Example – Part 3 – Exchange Impersonation
In part 3 of this series on integrating Exchange Web Services with Java and OpenEdge, we’re going to talk about a technique for accessing mailboxes called Exchange Impersonation. The first part of this article is going to talk about what it is, how it works, and the very serious risks it can potentially introduce to your enterprise. We’ll talk a little about how you can mitigate those risks, how to set it up from an administrative point of view, and then we’ll actually use it.
As with the other articles in this series, there is also a set of sample code that you can download and install to follow along later in the article.
Exchange Web Services – Subscriptions and Notifications
It’s been a really busy week since I posted my first post on Exchange Web Services. I have learned a lot in that short period of time that I want to share with you. Whether you are an OpenEdge, Java or .NET developer, I think this post is going to have some information for all of you.
In my first post, I told you about the background story – I need to enable an OpenEdge CRM application to create, modify and delete calendar and task items in Microsoft Exchange. I also need Exchange to let me know any time a calendar or task item is changed so that I can update the OpenEdge database accordingly. Simple use cases.
When I left off last week, my next step was to get Exchange subscriptions working, and, boy, what a trip that has been.