lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Armour (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LUCENENET-346) If Lucene.Net is used under ASP.NET with impersonation enabled, accessing directory at location requiring this impersonation will fail.
Date Thu, 04 Mar 2010 12:21:27 GMT

    [ https://issues.apache.org/jira/browse/LUCENENET-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841204#action_12841204
] 

Chris Armour commented on LUCENENET-346:
----------------------------------------

Without impersonation, under ASP.Net, it can be impossible to access files at network locations.
 So without adding impersonation on Lucene.Net threads, Merge etc. on an index in these circumstances
will fail as Lucene.Net is not honouring the Identity of the ASP.Net applications. 

> If Lucene.Net is used under ASP.NET with impersonation enabled, accessing directory at
location requiring this impersonation will fail.
> ---------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: LUCENENET-346
>                 URL: https://issues.apache.org/jira/browse/LUCENENET-346
>             Project: Lucene.Net
>          Issue Type: Bug
>         Environment: Windows XP, Windows Server 2003, IIS
>            Reporter: Chris Armour
>            Priority: Minor
>
> Upon closing an index writer, Merge can be called spawning another thread.  This new
thread doesn't have any knowledge of current ASP.NET impersonation.
> This is easily resolved by retrieving an System.Security.Principal.WindowsIdentity in
constructor of MergeThread (or possibly ThreadClass) if impersonation is active and  making
this WindowsIdentity available to the new thread itself.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message