Hmm.. I'm currently using the build from april 29th and still have the issue.
The LoginState is persisted in the apps local session, but that state
is not shared
with other webapps on the same virtual server when using request.login() instead
of form based login.
my app layout currently looks like this
main webapp, mounted on /
restful webservice, mounted on /rs
when using form based login, request.getUserPrincipal() returns the
correct principal in / and /rs
when using manual login (request.login()), the / webapp returns the
correct principal, while the /rs webapp returns just null.
Is this fix already in 3.0.1 from the 29th of april?
On Mon, May 10, 2010 at 6:56 PM, Bobby Bissett <bobby.bissett_at_oracle.com> wrote:
>>
>> "The programmatic login state does not necessarily persist in sessions
>> or participate in single sign-on."
>
> Because of the issue below, the login wasn't stored in the session until a
> recent fix:
>
> https://glassfish.dev.java.net/issues/show_bug.cgi?id=11340
>
> Could that be causing your problem? (If so, I think you'd also see that
> users aren't logged in after the initial request.)
>
> Cheers,
> Bobby
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>
--
Dominik Dorn
http://dominikdorn.com
Tausche Deine Lernunterlagen auf http://www.studyguru.eu/at/wu/ !