We recently upgraded to Exchange2K3/W2K3 from Exchange2K/W2K, and some of my
c# code that I used to access users' contacts using WebDAV has stopped
working. I'm getting a 401 unauthorized error. Hopefully, I can explain this
adequately.
Prior to the upgrade the following code was working properly.
FYI: The site was running in the context of the domain administrator, and
was also using the Administrator account to create a CredentialCache to
access Exchange
This function accepts my URI:
http://myMailServer/exchange/userLog.../?Cmd=contents
#region FetchContactsXm l
private string FetchContactsXm l(string sSourceURL)
{
StringBuilder sbPayload = new StringBuilder() ;
sbPayload.Appen d("<?xml version=\"1.0\" ?>");
sbPayload.Appen d("<a:searchreq uest xmlns:a=\"DAV:\ ">");
sbPayload.Appen d("<sql> SELECT \"urn:schemas:c ontacts:fileas\ " ");
sbPayload.Appen d(", \"urn:schemas:c ontacts:givenNa me\" ");
sbPayload.Appen d(", \"urn:schemas:c ontacts:sn\" ");
sbPayload.Appen d(", \"urn:schemas:c ontacts:o\" ");
sbPayload.Appen d("FROM Scope('SHALLOW TRAVERSAL OF \"\"') ");
sbPayload.Appen d("Where \"DAV:isfolder\ " = false AND \"DAV:contentcl ass\"
");
sbPayload.Appen d("= 'urn:content-classes:person' ");
sbPayload.Appen d(" ORDER BY \"urn:schemas:c ontacts:fileas\ " ASC");
sbPayload.Appen d("</>");
sbPayload.Appen d("</>");
// Array to hold Xml Payload
byte[] arPayload = null;
try
{
// Get Payload and Encode it to utf-8
arPayload = Encoding.UTF8.G etBytes((string )sbPayload.ToSt ring());
// Create HTTP Web Request & Set Properties
HttpWebRequest oWebRequest =
(System.Net.Htt pWebRequest)Htt pWebRequest.Cre ate(sSourceURL) ;
oWebRequest.Met hod = "SEARCH";
oWebRequest.Con tentType = "text/xml";
oWebRequest.Con tentLength = arPayload.Lengt h;
// Inject the Search Payload into the RequestStream
Stream oRequestStream = oWebRequest.Get RequestStream() ;
oRequestStream. Write(arPayload , 0, arPayload.Lengt h);
oRequestStream. Close();
// Set Credentials to Access Exchange Store
oWebRequest.Cre dentials = CreateCredentia lCache(sSourceU RL);
// Create the Web Response Object
System.Net.WebR esponse oWebResponse = (System.Net.Web Response)
oWebRequest.Get Response();
// Get the Xml Response Stream
Stream oStream = oWebResponse.Ge tResponseStream ();
// utf-8 handle it
Encoding oEncoding = System.Text.Enc oding.GetEncodi ng("utf-8");
StreamReader oStreamReader = new StreamReader(oS tream, oEncoding);
// Get the WebDAV Xml into a string
string sXmlData = oStreamReader.R eadToEnd();
// Clean Up
oStreamReader.C lose();
oStream.Close() ;
oWebResponse.Cl ose();
// Return the Xml string
return sXmlData;
}
catch (Exception oException)
{
ExceptionManage r.Publish(oExce ption);
throw(oExceptio n);
}
}
#endregion
#region CreateCredentia lCache
private CredentialCache CreateCredentia lCache(string sSourceURL)
{
try
{
CredentialCache oCredentialCach e = new CredentialCache ();
oCredentialCach e.Add(
new System.Uri(sSou rceURL),
"NTLM",
new NetworkCredenti al(
ConfigurationSe ttings.AppSetti ngs["ExchangeAdminA ccount"].ToString(),
@ConfigurationS ettings.AppSett ings["ExchangeAdminA ccountPwd"].ToString(),
ConfigurationSe ttings.AppSetti ngs["DomainName "].ToString()));
return oCredentialCach e;
}
catch (Exception oException)
{
ExceptionManage r.Publish(oExce ption);
throw(oExceptio n);
}
}
#endregion
As I said, all of this worked perfectly before the upgrade. Now apparently
Exchange 2003 doesn't allow the Administrator account to have permissions on
all other account by default - which is a good thinkg since I shouldn't have
been using that anyway. So our exchange admin created an account for me to
use with the necessary permissions.
I verified that the account he created can access a user's contacts folder
by browsing to http://myMailServer/exchange/userLog.../?Cmd=contents
and logging in as DOMAIN\account, password. I was able to open any user's
contacts folder that I wanted to.
Ok, so after the upgrade, the code breaks at the following spot:
Stream oRequestStream = oWebRequest.Get RequestStream() ;
I noticed that this is before I even attached the CredentialCache , so I
tried moving that to above that point in code, but no change.
The exact exception is:
The remote server returned an error: (401) Unauthorized.
When building the CredentialCache in the CreateCredentia lCache function, I
am using that new account I noted that our exchange admin created.
Any help is appreciated.
