Problems w/ 2.0.3 & WIndows Authentication
I'm not able to get 2.0.3 work configured for windows authentication.
See this thread:
http://community.countersoft.com/forums/thread/515.aspx
Can someone help?
Thanks,
Yarko
|
yarkot
· 1 |
|
| Monday, February 27, 2006, 6:07:15 PM | |
0
|
We are trying to replicate the issue with no success. We think it might be to do with cookie or cache, can you try and clear them? |
||||
|
|||||
0
|
Have cleared cache, cookies, forms, etc. no change. WRT cookies - this is relevant web.config portion: <sessionState ----- I'm following my "normal" deployment pattern:
I'm stuck at the first step (didn't even try the second). Could this be an issue w/ session state connection string in the presence of WinAuthentication config? In IIS, the "Authentication" methods set for this are (unchecked) Anonymous access; (Integrated Windows Authentication) for Authenticated Access; Regards, Yarko |
||||
|
|||||
0
|
Yarko, Are you using an old web.config file? Please be aware that the web.config that comes with 2.0.3 must be used as it has some new entries. Also make sure that "Anonymous Access" is NOT ticked in the directory security access options of IIS. Is your connection string correct? Can you please try and install: http://www.iewatch.com and send us the log this generates? This will help us with finiding the issue. Thanks, Saar. |
||||
|
|||||
0
|
Using a complete snapshot from the new distribution (and using a diff tool to manage the text changes in web.config from my 2.0.2 to fresh 2.0.3). RE: Connection string: This install / web.config works fine if ALL I do is thange from Windows to Forms authentication. I dont' have permissions to attached the "iewatch" log file.... it's tail end item is this (I'll mail the file separately): .... <ITEM time="17:27:43.733" duration="0.000" method="GET" url="http://localhost/favicon.ico"> |
||||
|
|||||
0
|
Can you please paste your web.config file? The only way we can replicate this is by commenting out the new httpModules section. |
||||
|
|||||
0
|
I've emailed it (to preserve confidentiality, while not changing anything in the way I had it configured). |
||||
|
|||||
0
|
We didn't receive anything yet, Where did you email this to? Please re-send to priority@countersoft.com (paste the contents of the file).
|
||||
|
|||||
0
|
Mark wrote: Hi,Thanks for this. The problem is that you have commented out the following section: <!-- AUTHENTICATION (Gemini possible modes are "Windows", "Forms") -->--------------------- Yes – that did the trick, but this assumption / “mistake” is easy to make – and also, will note it has up until now ALWAYS worked in the "mistaken way". To see WHY it is NATURAL to do this, take a look at my config file for 1.9.1 (configured for Windows Authentication): <!-- AUTHENTICATION Gemini possible modes are "Windows", "Forms" --> <authentication mode="Windows"> <!-- <authentication mode="Forms"> <forms name="Gemini191" loginUrl="Default.aspx" path="/" > </forms> --> </authentication> NOTE: “<forms…” is INDENTED relative to <authentication mode=”Forms”> => therefore it is QUITE NATURAL (if in error) to assume these are related to Forms authentication. SUGGEST: un-indent “<forms…” section so it does not look like a “child” of the line above it; also perhaps adding a comment just before to the effect: <!-- The following forms section is for both authentication modes; be sure to set form name to be unique for your Gemini installation. -->Kind regards, Yarko |
||||
|
|||||




