Mailing-List: contact shiro-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: shiro-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of brian.demers@gmail.com
 designates 209.85.160.175 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=eDwS50u7kbDhTp3zSvxFByNMIzkr4YOUS4FHCPRcj5BXF0gMklG2WbtluaJvzAfAaH
         ZzNwETukpUHR+cwaP+Fz19srL5Kgi+QgJyrlK9iyMevcA9C5OSrEVulkpfQbB8CemPYE
         zluQaw6/HMQ60hQnNxem5x/zwq4udd/KGaac0=
MIME-Version: 1.0
Date: Tue, 11 May 2010 09:33:27 -0400
Message-ID: <AANLkTin_dCIsz5CSXEm-u7nQbIK0h91GFWSF0MaYzRyV@mail.gmail.com>
Subject: Status of 'Run As'?
From: Brian Demers <brian.demers@gmail.com>
To: shiro-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=000e0cd733f80ff715048651929e

--000e0cd733f80ff715048651929e
Content-Type: text/plain; charset=ISO-8859-1

Hey guys,

I was just wondering the status of 'Run As' support (Assume Identity, I
think there where a few other terms that where thrown around too)
https://issues.apache.org/jira/browse/SHIRO-25

I took a look at that patches and reread the previous threads.  I am
assuming this isn't going to make the 1.0 ( can we bump the jira 'fix for'
version? )

To get this support in the past.  I have done the following:

        DelegatingSubject fakeLoggedInSubject = new DelegatingSubject(
principal, /* authenticated */ true, null, null, /* Non-web */
securityManager );
        // fake the login
        ThreadContext.bind( fakeLoggedInSubject );


We are not using this in production yet, but in my web app I need to use two
different SecurityManagers, one for the Web (bound to http requests) and the
default one, for this 'run as' support.  We would be using the 'run as' to
run scheduled task (so there is no access to http requests)

Are there flaws behind this approach?

Will / does the the official support for this get around the
WebSecurityManagers need for a http request?

Thanks,
Brian

--000e0cd733f80ff715048651929e--