Sorry about the repost; had incorrect managed groups ID last time!

Hi,

I'm having a problem with a web service; specifically a custom
UsernameTokenManager which needs to access a remote database. The web
service is set up in IIS to use anonymous access with a UserID and Password
provided, and the web.config file is set up to impersonate and use windows
authentication; the problem comes when the request is sent to the service.

The web service needs to access a database on a remote server, and needs to
use the UserID and Password held in the IIS config; the problem is during
testing I'm noticing that during my authentication phase (my custom
UsernameTokenManager class) the database access is done via the ASPNET
user - once this has been authenticated then the rest of the application
uses the correct UserID and Password for data access. I'm (guessing) that
this would be using the NetworkService account on Server 2003.

The production SQL Server database will not accept the ASPNET or
NetworkService accounts, access must be done through the UserID and Password
provided in IIS.

I'm pretty much pulling my hair out now trying to work out how/why is the
UsernameTokenManager class is running under the default account; how can I
change this to run under the specified account settings for the rest of the
application?

Cheers,
Dave