deltaspike-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gerhard Petracek <gerhard.petra...@gmail.com>
Subject Re: Coming in late to discuss @Secured
Date Sun, 18 Mar 2012 12:02:53 GMT
hi alan,

no - after the security check the state is VIOLATION_FOUND
or NO_VIOLATION_FOUND (see invokeVoters in [1]).

regards,
gerhard

[1] http://s.apache.org/xa



2012/3/18 Alan D. Cabrera <list@toolazydogs.com>

> Is it thought that the "ongoing security check" is some relatively longer
> running conversation that exists longer than the vote in which the voters
> participate?
>
>
> Regards,
> Alan
>
>
> On Mar 17, 2012, at 11:38 AM, Gerhard Petracek wrote:
>
> > hi alan,
> >
> > e.g.:
> > in myfaces codi it is used in custom cdi-contexts. they can check the
> state
> > and in case of an ongoing security check, the scope shouldn't change its
> > internal state.
> >
> > regards,
> > gerhard
> >
> >
> >
> > 2012/3/17 Alan D. Cabrera <list@toolazydogs.com>
> >
> >> In DELTASPIKE-64 there's a paragraph that states:
> >>
> >>> in addition an AccessDecisionVoterContext is needed to detect if there
> >> is an ongoing security check (e.g. it's possible to use it in a custom
> >> scope to avoid that a security check postpones the expiration).
> >>
> >>
> >> I'm sure that I'm being dense but can someone provide a little bit more
> >> detail what this means?  is the "ongoing security check amongst voters"
> the
> >> current vote or is there a larger process in motion?
> >>
> >>
> >> Regards,
> >> Alan
> >>
> >>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message