On the subject of Windows authentication…
We have been seeing an issue where a user becomes completely unable to
login through the Office 2003 Add-In. Typically the user is on a Windows
client which is part of a domain, but the Alfresco server in question is
simply using Alfreco's standalone internal authentication for the time being.
We are not trying to authenticate against the domain, and the usernames
are different.
The symptoms are that instead of seeing the Add-In's small pop-up
prompt for credentials, the user receives a minature version of the
Web Client login page. However, the user is completely unable to login;
in fact, it is impossible to login with any credentials.
Further investigation reveals that the problem can usually be solved only
by logging out of the Windows machine entirely! Furthermore, a login
of sorts can be forced through the Add-In by deleting the CIFS server
configuration.
My guess here is that Windows is doing its usual over-stubborn cacheing
of login credentials for CIFS, but for some reason these credentials are
also being used for the Add-In's HTTP login and failing. My first guess
would by that Windows is pre-pending the Windows Computer Name of
the Alfresco CIFS server to the username as a login domain, which works
fine for a the CIFS server, but then fails for the HTTP. Trouble is, the
Add-In is often unhappy unless the user is pre-authenticated against a
network location on the CIFS server…
For what it's worth, I've removed all sites from the Local intranet security
zone under Windows' Internet Options, and set all zones to 'Prompt for
Username and Password' for Logon Authentication, but this hasn't helped.
ops: I think "loading an Office document using WebDAV via Windows Explorer" is not the same with read/write files from/to some network place, isn't it? Is that Web Folder some special organized folder? How can check that possibility?
