Re: Windows authentication for web service client??

I'm having a similar problem

I have a web service that make a webDav request to Exchange.

I have impersonation on but when I use the defaultCredentials in the web
services to make the webdav reqeust I get an Unauthorized 401 error. My
credentials have rights to make this request and I'm at my wits end trying
to figure it out.

The service works if I hard code my Network credentials in the service but
does not otherwise.

Any help with this would also be appreciated.

Thanks,
Dan


"Kevin Yu" <koo9@xxxxxxxxxxx> wrote in message
news:eOariLKQFHA.1476@xxxxxxxxxxxxxxxxxxxxxxx
> but the problem with impersonation in the code is after LogonUser() win32
> call, will the defaultcredentials be set to the new credentials then?
>
>
>
>
>
> "Kevin Yu" <koo9@xxxxxxxxxxx> wrote in message
> news:OEbaAMIQFHA.2356@xxxxxxxxxxxxxxxxxxxxxxx
>>I think impersonation will do , enable impersonation but don't specified
>>the user, use code call the web service with a different
>>username/password.
>>
>>
>>
>> "Brock Allen" <ballen@xxxxxxxxxxxxxxxxx> wrote in message
>> news:453919632490103600068528@xxxxxxxxxxxxxxxxxxxxxxx
>>> The ASPNET account is a local account, so the other machine or domain
>>> wouldn't know about it. You can either run you web app under a different
>>> account, but that affects the rest of the code in there too. The other
>>> approach is to have a dedicated account (instead of using the current
>>> identity of ASPNET) that you can use to do the authentication and then
>>> use those credentials from the client.
>>>
>>> -Brock
>>> DevelopMentor
>>> http://staff.develop.com/ballen
>>>
>>>
>>>
>>>> hi all
>>>>
>>>> got a question here, a web service secure mode is set to "windows", on
>>>> the client side
>>>>
>>>> when supplying the credentials, it's like this:
>>>>
>>>> somewebservice.Authentication ssoAuth = new
>>>> somewebservice.Authentication();
>>>>
>>>> ssoAuth.PreAuthenticate = true;
>>>>
>>>> ssoAuth.Credentials = System.Net.CredentialCache.DefaultCredentials;
>>>>
>>>> from the info here
>>>>
>>>> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref
>>>> /html/frlrfSystemNetCredentialCacheClassDefaultCredentialsTopic.asp
>>>>
>>>> the defaultcredential should supply the current security context that
>>>> the client is running, but in my case the client is another web
>>>> service running
>>>>
>>>> on another server, now by default the account that the client(the
>>>> calling web service) is running under ASPNET account,
>>>>
>>>> so on the host(somewebservice), I should add the clientdomain\ASPNET
>>>> account into the windows account?
>>>>
>>>
>>>
>>>
>>
>>
>
>


.

Relevant Pages

  • Re: SetPassword access denied
    ... That said, I think one thing worth pointing out is that in both cases here, your code is supplying credentials to the DirectoryEntry constructor. ... the identity of the current thread (established either via impersonation or using the process token without impersonation) is NOT the account that is used for performing remote activities in the directory. ... Co-author of "The .NET Developer's Guide to Directory Services Programming" ...
    (microsoft.public.windows.server.active_directory)
  • Re: Issue with ASP.NET client, COM Interop, and Identity impersonation
    ... When I switch off impersonation, the identity on COM side is ... under a local machine account and thus, ... >> AspCompat mode and it does not help much. ... >> is another application, a web service, that uses the same set of COM ...
    (microsoft.public.dotnet.languages.vc)
  • Re: Issue with ASP.NET client, COM Interop, and Identity impersonation
    ... When I switch off impersonation, the identity on COM side is ... under a local machine account and thus, ... >> AspCompat mode and it does not help much. ... >> is another application, a web service, that uses the same set of COM ...
    (microsoft.public.dotnet.framework)
  • Re: Issue with ASP.NET client, COM Interop, and Identity impersonation
    ... When I switch off impersonation, the identity on COM side is ... under a local machine account and thus, ... >> AspCompat mode and it does not help much. ... >> is another application, a web service, that uses the same set of COM ...
    (microsoft.public.dotnet.framework.interop)
  • Re: Issue with ASP.NET client, COM Interop, and Identity impersonation
    ... When I switch off impersonation, the identity on COM side is ... under a local machine account and thus, ... >> AspCompat mode and it does not help much. ... >> is another application, a web service, that uses the same set of COM ...
    (microsoft.public.dotnet.framework.aspnet)