aspnet username / machine.config
-
I have a website that is created in asp.net that needs read access to certain files on the network. Since the aspnet username doesn't have access rights it can't read the file on the network. What's the proper method or steps to setup the machine.config if I want to grant access to the network files. Of course, I want to prevent hackers from looking into the machine.config file, and looking at the username and password. Do I have to change the username or password in the machine.config file? Do I have to change anything on IIS ver 5.01? How is the user account, ASPNET created on the network? Thanks!
-
I have a website that is created in asp.net that needs read access to certain files on the network. Since the aspnet username doesn't have access rights it can't read the file on the network. What's the proper method or steps to setup the machine.config if I want to grant access to the network files. Of course, I want to prevent hackers from looking into the machine.config file, and looking at the username and password. Do I have to change the username or password in the machine.config file? Do I have to change anything on IIS ver 5.01? How is the user account, ASPNET created on the network? Thanks!
The best way, I guess is to map to the network computer which you want to access as if it is a local drive. And then, while sharing the drive on the network, you can set permissions on the folder which you wanted access including the user or Anomnymous user. Or I think, we can also impersonation to run the app in a particular user context which can be specified in section of web.config. I do not think, we need to change anything in Machine.Config to set this up and personally do not suggest to modify Machine.Config, unless strictly necessary. Hope this helps Bhaskara
-
The best way, I guess is to map to the network computer which you want to access as if it is a local drive. And then, while sharing the drive on the network, you can set permissions on the folder which you wanted access including the user or Anomnymous user. Or I think, we can also impersonation to run the app in a particular user context which can be specified in section of web.config. I do not think, we need to change anything in Machine.Config to set this up and personally do not suggest to modify Machine.Config, unless strictly necessary. Hope this helps Bhaskara
Bhaskra is correct. You can create a new user (in your Domain or Local computer) in which the web app runs under IIS. (Under the directory security tab). Then under the web.config for the app, you can do the following:
This will make the app run under that user rather than the ASPNET user. ~javier lozano (blog || email)
-
Bhaskra is correct. You can create a new user (in your Domain or Local computer) in which the web app runs under IIS. (Under the directory security tab). Then under the web.config for the app, you can do the following:
This will make the app run under that user rather than the ASPNET user. ~javier lozano (blog || email)
-
The best way, I guess is to map to the network computer which you want to access as if it is a local drive. And then, while sharing the drive on the network, you can set permissions on the folder which you wanted access including the user or Anomnymous user. Or I think, we can also impersonation to run the app in a particular user context which can be specified in section of web.config. I do not think, we need to change anything in Machine.Config to set this up and personally do not suggest to modify Machine.Config, unless strictly necessary. Hope this helps Bhaskara