myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gerhard Petracek (Resolved) (JIRA)" <...@myfaces.apache.org>
Subject [jira] [Resolved] (EXTCDI-229) Optional SecurityViolationHandler
Date Tue, 27 Sep 2011 13:15:11 GMT

     [ https://issues.apache.org/jira/browse/EXTCDI-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gerhard Petracek resolved EXTCDI-229.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.0.2
    
> Optional SecurityViolationHandler
> ---------------------------------
>
>                 Key: EXTCDI-229
>                 URL: https://issues.apache.org/jira/browse/EXTCDI-229
>             Project: MyFaces CODI
>          Issue Type: Improvement
>          Components: Core, JEE-JSF12-Module, JEE-JSF20-Module
>    Affects Versions: 1.0.1
>            Reporter: Michael Kurz
>             Fix For: 1.0.2
>
>
> I use @Secured with a custom AccessDecisionVoter checking if a user is logged in. If
the user is not logged in I only want to redirect to the login page. Currently it is not possible
to do this without creating a message in the FacesContext.
> As discussed with Gerhard, a simple solution for this would be an optional SecurityViolationHandler.
If there is a bean for this type, it is used to handle SecurityViolation instances created
in the voter. If not, the default behavior (adding messages to the facesContext) should be
used.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message