Skip to main content.
home | support | download

Back to List Archive

Re: swish-e vs ASP.NET secured site

From: Seth Eilbott <seilbott(at)>
Date: Fri Oct 24 2003 - 18:27:30 GMT
On Fri, Oct 24, 2003 at 01:04PM -0600, Ed Bomke wrote:
> We're evaluating search tools for use in our extranet, based on ASP.NET 
/ C# .  We use forms authentication for the site, so any indexing solution
> coming through the front door would presumably need to deal with that 
issue.  Has anyone out there been successful adapting swish-e for such a
> scenario ?  Any workaround which would leave swish-e as-is ?

Why would the indexing solution have to deal with authentication?  IMO,
the authentication should be separate from indexing and searching.

We use swish-e as the engine for indexing/searching here, on top of
an Apache server.  Apache itself (with plugins) performs ALL 
and authorization functions before our application gets control; in fact,
our application knows NOTHING about it, aside from being given the
authenticated user name.  (If authentication fails, our app never even
gets invoked.)


Due to deletion of content types excluded from this list by policy,
this multipart message was reduced to a single part, and from there
to a plain text message.
Received on Fri Oct 24 18:41:05 2003