RE: Webdav Authentication



The only way (I can think of) that you could possibly achieve this is to
have a FE/BE architecture (front end/back end). You can turn anonymous
access on on your front end and keep IWA/Basic turned on on your back end.
The FE is always going to need to communicate to the BE with IWA or Basic
authentication because mailboxes are tightly coupled with Active Directory.
I would not recommend running your FE in anonymous mode though. The better
architecture is to do it the way you already are doing it and store the
credentials with your app server. That is a common scenario by many
application developers.
I'm curious what you would be trying to do with WebDAV where you WOULDN'T
want to pass in credentials or why that is a problem.

Patrick
Microsoft Enterprise Business Apps Messaging Development

--------------------
| Thread-Topic: Webdav Authentication
| thread-index: AcYYf5JSykTSoMn/QIWXaNBkIIKMZA==
| X-WBNR-Posting-Host: 65.160.61.218
| From: "=?Utf-8?B?RWRicm93bg==?=" <Edbrown@xxxxxxxxxxxxxxxxxxxxxxxxx>
| Subject: Webdav Authentication
| Date: Fri, 13 Jan 2006 12:26:02 -0800
| Lines: 14
| Message-ID: <1E7341CF-5680-42D5-B115-DD21BD8D488D@xxxxxxxxxxxxx>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.exchange.development
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.exchange.development:7190
| X-Tomcat-NG: microsoft.public.exchange.development
|
| We have an application that communicates with Exchange via webdav. Our
| application server is not necessarily a Microsoft server, so I am
currently
| storing the Exchange credentials user/password in our application
server.
| Any client browser can then connect to our appserver and communicate with
| Exchange. We are looking for a way to connect to Exchange via Webdav
without
| having to store the credentials on our appserver. I have seen postings
on
| Kerberos and other mechanisms but have not seen a real solution posted.
Keep
| in mind our appserver could be a unix/solaris server. So is there
anyway
| that a client connecting to our appserver be authenticated so he can
connect
| to exchange.
|
| Thanks in advance,
|
| Ed
|

.



Relevant Pages

  • Re: WebDAV mark as read?
    ... perfect with Exchange server 2003 but this is not working with Exchange ... Best Regards ... we are really newbies on webdav and struggling to make things moving.. ...
    (microsoft.public.exchange.applications)
  • Re: Public Task List
    ... Henning Krause ... Try my free Exchange Explorer: ... >> is the Webserver on the same machine as the Exchange server? ... >> Another choice could be WebDAV, which is an extension of the HTTP ...
    (microsoft.public.exchange.development)
  • Re: Receiving ldap error -17709 in Entourage on a Mac / SBS 2003
    ... Small business Server 2003 SP1 running Exchange SP1. ... The server is running IMAP4 and File services for the Macintosh. ... Entourage should connect to Exchange via WebDAV. ...
    (microsoft.public.windows.server.sbs)
  • 409 Conflict when sending mail using WebDAV
    ... from the Exchange 2003 SDK for sending a mail message using WebDAV. ... The remote server returned an error: ... I can read the messages from the mailbox using WebDAV, ... I'm using a HTTP connection and instead of using ...
    (microsoft.public.exchange.development)
  • Re: CDO Created Appointments do not show in Calendar view, though do show in By Category??
    ... Microsoft explains similar problem with WebDAV here: ... If you need WebDAV API for Exchange server, ... > I'm creating Appointments in my calendar by running some VB Code talking ...
    (microsoft.public.exchange2000.development)