K
Kevin Jackson
If I turn off anonymous access to an ASP page and then use "Integrated
Authentication" in a Intranet environment, I expected the user context to be
the user who is accessing the page. It doesn't seem to be the case.
I'm using a component (ASPUpload) to move a file to a share point on another
box. The user context that I thought I was running under has write access
to this share but I keep getting a 500 back when I run the page. Local
paths work fine, share points are a no go.
I turned to basic authentication, put the name of the domain in the domain
box and then used the same username and password to access the page and it
copied the file with no problems. So in this case it seems that the user
context WAS the user I expected.
What am I missing that I cannot get Integrated Authentication to work in the
expected user context?
Any ideas?
Authentication" in a Intranet environment, I expected the user context to be
the user who is accessing the page. It doesn't seem to be the case.
I'm using a component (ASPUpload) to move a file to a share point on another
box. The user context that I thought I was running under has write access
to this share but I keep getting a 500 back when I run the page. Local
paths work fine, share points are a no go.
I turned to basic authentication, put the name of the domain in the domain
box and then used the same username and password to access the page and it
copied the file with no problems. So in this case it seems that the user
context WAS the user I expected.
What am I missing that I cannot get Integrated Authentication to work in the
expected user context?
Any ideas?