Web services and password change in AD.

[Luc]

Hi everyone,

I had this strange problem. We are using web services for our entreprise
applications. We are using IIS as the host for our webservices and IIS is
configured to use integrated authentication.

The problem arise when the user's password changes and he has not done it at
logon time. So it seams that at that specific time, the transaction goes to
IIS and bounces back with an http status 401: Unauthorized.

Since we cannot force the user to change his password at logon time on
WinXP, is there a way to protect ourself in making a web service transaction
in order for it not to return an http 401: unautorized?

Can someone explain how this process is working?

Any snippet of code supporting the solution?

Thank's for any help.

[Abhi]

Luc,

I am accessing AD using WS's. I am asking my clients to set the
UseDefaultCredentials property to true before calling any of the ws methods
and it works. for example:

MyWebServices service = new MyWebServcies;
service.UseDefaultCredentials = true.

This might help you.

"Luc" wrote:

Hi everyone,

I had this strange problem. We are using web services for our entreprise
applications. We are using IIS as the host for our webservices and IIS is
configured to use integrated authentication.

The problem arise when the user's password changes and he has not done it at
logon time. So it seams that at that specific time, the transaction goes to
IIS and bounces back with an http status 401: Unauthorized.

Since we cannot force the user to change his password at logon time on
WinXP, is there a way to protect ourself in making a web service transaction
in order for it not to return an http 401: unautorized?

Can someone explain how this process is working?

Any snippet of code supporting the solution?

Thank's for any help.

[Luc]

Thank's for this valuable answer.

Can you just tell me what this attribute means in order for me to better
understand how it work's

Thank's again

"Abhi" wrote:

Luc,

I am accessing AD using WS's. I am asking my clients to set the
UseDefaultCredentials property to true before calling any of the ws methods
and it works. for example:

MyWebServices service = new MyWebServcies;
service.UseDefaultCredentials = true.

This might help you.

"Luc" wrote:

Hi everyone,

I had this strange problem. We are using web services for our entreprise
applications. We are using IIS as the host for our webservices and IIS is
configured to use integrated authentication.

The problem arise when the user's password changes and he has not done it at
logon time. So it seams that at that specific time, the transaction goes to
IIS and bounces back with an http status 401: Unauthorized.

Since we cannot force the user to change his password at logon time on
WinXP, is there a way to protect ourself in making a web service transaction
in order for it not to return an http 401: unautorized?

Can someone explain how this process is working?

Any snippet of code supporting the solution?

Thank's for any help.

[Abhi]

By setting that property to true you are identifying yourself to IIS as an
authenticated windows users which IIS can use to access Active Directory
services and get you the results. There is an article in msdn.microsoft.com
for using active directory services via web services. That would be helpful
to further understand this thing.

-Abhi

"Luc" wrote:

Thank's for this valuable answer.

Can you just tell me what this attribute means in order for me to better
understand how it work's

Thank's again

"Abhi" wrote:

Luc,

I am accessing AD using WS's. I am asking my clients to set the
UseDefaultCredentials property to true before calling any of the ws methods
and it works. for example:

MyWebServices service = new MyWebServcies;
service.UseDefaultCredentials = true.

This might help you.

"Luc" wrote:

Hi everyone,
>
I had this strange problem. We are using web services for our entreprise
applications. We are using IIS as the host for our webservices and IIS is
configured to use integrated authentication.
>
The problem arise when the user's password changes and he has not done it at
logon time. So it seams that at that specific time, the transaction goes to
IIS and bounces back with an http status 401: Unauthorized.
>
Since we cannot force the user to change his password at logon time on
WinXP, is there a way to protect ourself in making a web service transaction
in order for it not to return an http 401: unautorized?
>
Can someone explain how this process is working?
>
Any snippet of code supporting the solution?
>
Thank's for any help.