[ 
http://wicketstuff.org/jira/browse/WSSWARM-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Maurice Marrink resolved WSSWARM-6.
-----------------------------------

    Resolution: Fixed

Integrated in wasp is now logging functionality to log denied actions from 
WaspAuthorizationStrategy#isActionAuthorized. these log messages are stored in 
the requestcycle meta data and can be printed at any time during the request 
(until cleared). The default is to log a debug message trough the logging 
implementation but this is easily changed by overwriting the logMessage method. 
By default logging is disabled until debug logging is enabled through the 
logging implementation for example 
log4j.category.org.apache.wicket.security.strategies.WaspAuthorizationStrategy=DEBUG

> enhanced permission denied logging
> ----------------------------------
>
>                 Key: WSSWARM-6
>                 URL: http://wicketstuff.org/jira/browse/WSSWARM-6
>             Project: WicketStuff SWARM
>          Issue Type: Improvement
>    Affects Versions: 1.3.1
>            Reporter: Maurice Marrink
>         Assigned To: Maurice Marrink
>            Priority: Minor
>             Fix For: 1.3.1
>
>
> Summary: It would be nice to have custom error messages capable of displaying 
> in detail what was denied.
> Full request: http://markmail.org/message/bik6p4kujslpcqxg
> Possible solution: Session.error and wicket propertyfiles
> TODO: check how much can become part of the wasp api

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://wicketstuff.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to