Hello.
I hope someone has some insight for me on this.
When impersonate=true is used, which system folders need configuring for user access? (I added group access to the Temporary ASP.Net folder, e.g.--I'm using security groups from AD).
This application also reads an *.csv file using Microsoft ODBC DSN, so I granted RW permissions for the group and ASPNet to the TMP system variable defined folder.
Neither of these worked, however.
I took impersonate out to deal with that later (Without impersonate=true, I don't get the WindowsPrincipal Identity.Name when the user first hits the site in the browser (ASPNet is the account instead)).
Meanwhile, authentication continues to be something of a challenge. When I use a test network account (which is a member of the group) to run the web app, this account gets multiple challenges. What causes that? I've already authenticated into the network at sign-on. I've assigned the group RX permissions on the web folder. I've given ASP.Net RX. The funny thing is, there's no handling of the group membership in the code (no isInRole stuff yet. That'll come later)--just the web.config file. Though this account seems to fail authentication (3 challenges), the app loads in the background anyway. Other *real* users, though they're authenticated in the network, still get a challenge when they hit the app for the first time. Don't know why .....And if impersonate=true, they may not authenticate at all, which leads back to my first question about those system folders.
Does anyone know a good source to figure out NTFS and groups and roles?
*Many thanks*
Tess
