On 9/26/06, Jim Wilson <[EMAIL PROTECTED]> wrote:
I'd do it, but I'm too busy being consumed with worries about the lack of
support for HTTP/NTLM credentials and SMB fileshare indexing.
Arrrgg - tis another sad day in the life of this pirate.
We seem to share the same problems...they haven't gone and knocked me
down...yet, but I expect they might fairly soon.
For now, I'm placing the shares under an IIS umbrella: I direct the
crawl to the root of the web and serve http links to the files. IIS
(somehow) takes care of A/D authorization: once the user clicks on a
link, IIS checks the users credentials and matches it to the files ACL
(I suppose). The downsides? Even though I could theoretically allow
the users with sufficient privileges to write files, I can only
provide WebDAV access. Whats more, I'm stuck with
IIS/Windows/whatever. I'd much rather let the customer decide what he
wants to run on his servers. Finally, distributed network shares (i.e.
shares not shared from the server) make the problem/solution
significantly more complicated.
Alternatively, you could try with the file protocol, generating
"browser unfriendly" file:// links, opens up it's own Pandora's box of
security issues...so, how do you go about it?
t.n.a.
