Is it ok to use impersonation in the web.config file for a web service?
Let me tell you why I ask. My web service to ultimately connection to a sql
server database. The recommended way to connect to SqlServer is to use a
trusted connection (nt authentication etc), but inorder for me to do this I
want to change the user my webservice (aspnet_wp) is running under - don't
I? Hence the use of the Impersonation element in the web.config file. I
suppose I could use normal authentication to SqlServer but that means I have
to keep a username and password somewhere.
BYW, I'm using WSE 2.0 for authentication - don't know if this would make a
difference.
Thanks for any help
Graham Allwood
Girish bharadwaj - 11 Sep 2004 11:35 GMT
Well, you can potentially run a different "Datalayer" component under a
different user who can access the database.
> Is it ok to use impersonation in the web.config file for a web service?
>
[quoted text clipped - 12 lines]
>
> Graham Allwood
Jared - 11 Sep 2004 13:26 GMT
Gravy,
Once your user is authenticated to your web service, does every user
require/get access to the database? If so, and they all get the same access,
then allowing access to the ASPNET account will do what you want. If you
need to enforce non-repudiation, or sql security then you will want to
impersonate the user. It all comes down to what you need to do with the
credentials, fact remains, they did supply the correct credentials to access
the service.
Jared
> Is it ok to use impersonation in the web.config file for a web service?
>
[quoted text clipped - 12 lines]
>
> Graham Allwood