geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ivan <xhh...@gmail.com>
Subject Re: Default Subject configuration for Jetty assembility
Date Tue, 21 Jul 2009 07:55:55 GMT
Seem, it still does not work.
I did not find those codes like "ContextManager.setCaller()" in the
SecurityHandler, so, did not think that the defaultSubject in attached to
the current thread.

2009/7/21 David Jencks <david_jencks@yahoo.com>

> Well, its a bug :- )https://issues.apache.org/jira/browse/GERONIMO-475<https://issues.apache.org/jira/browse/GERONIMO-4756>
> 6
> I think I fixed it but don't have a test case handy.  Could you check?
>
> thanks
> david jencks
>
> On Jul 20, 2009, at 4:39 AM, Trygve Hardersen wrote:
>
> I'm also having this problem. Are you saying it will work if I configure
> JASPI authentication?
>
> Thanks
>
> Trygve
>
> On Mon, Jul 20, 2009 at 11:17 AM, Ivan <xhhsld@gmail.com> wrote:
>
>> Hi,
>>    While working with the current 2.2 Jetty assembility, I found that the
>> way we used to configure the default subject does not take effect again.
>>    After checking the codes, it seems that, currently, jetty builder will
>> always check for the jaspi authentication configuration, if not found, the
>> runassource will be ignored.
>>   I wonder whether it is by design or an issue. Thanks for any comment !
>>
>> --
>> Ivan
>>
>
>
>


-- 
Ivan

Mime
View raw message