You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Ivan <xh...@gmail.com> on 2009/07/20 11:17:04 UTC
Default Subject configuration for Jetty assembility
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
Re: Default Subject configuration for Jetty assembility
Posted by David Jencks <da...@yahoo.com>.
Bug, https://issues.apache.org/jira/browse/GERONIMO-4756, Thanks!
david jencks
On Jul 20, 2009, at 2:17 AM, Ivan 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
Re: Default Subject configuration for Jetty assembility
Posted by Trygve Hardersen <tr...@jotta.no>.
I'll start working on getting our app to run with Geronimo 2.2 & Jetty7
today. We're currently using Jetty6 because of security configuration
problems.
Will let you know what I find.
Thanks
Trygve
On Tue, Jul 21, 2009 at 9:55 AM, Ivan <xh...@gmail.com> wrote:
> 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 <da...@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 <xh...@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
>
Re: Default Subject configuration for Jetty assembility
Posted by Ivan <xh...@gmail.com>.
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 <da...@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 <xh...@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
Re: Default Subject configuration for Jetty assembility
Posted by David Jencks <da...@yahoo.com>.
Well, its a bug :- )https://issues.apache.org/jira/browse/GERONIMO-4756
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 <xh...@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
>
Re: Default Subject configuration for Jetty assembility
Posted by Trygve Hardersen <tr...@jotta.no>.
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 <xh...@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
>