G
Guest
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.
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.