[
https://issues.apache.org/jira/browse/SHIRO-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13435922#comment-13435922
]
david e. berry commented on SHIRO-160:
--------------------------------------
Please read the entire thread. All the code to connect shiro to graniteds is
attached to this ticket. The graniteds war is an example war which shows it
working. To my knowledge, this code has not been added into the shiro project
yet, but you are free to use it. If you use the code please make the change
included in the notes above:
Change logout in GraniteDSSecurityService to:
public void logout() throws SecurityServiceException {
Subject currentUser = SecurityUtils.getSubject();
logger.debug("logging out the user:" + currentUser.getPrincipal());
currentUser.logout();
HttpGraniteContext context =
(HttpGraniteContext)GraniteContext.getCurrentInstance();
if (context.getRequest().getSession(false)!=null){
endLogout();
}
}
Dave
> Flex integration with Shiro
> ---------------------------
>
> Key: SHIRO-160
> URL: https://issues.apache.org/jira/browse/SHIRO-160
> Project: Shiro
> Issue Type: New Feature
> Components: Authentication (log-in), Authorization (access control)
> Affects Versions: Incubation
> Reporter: david e. berry
> Labels: Flex
> Attachments: amf package layout.png, blazeds-war-1.0-SNAPSHOT.war,
> graniteds-war-1.0-SNAPSHOT.war, shiroflex-1.2.0.tgz, shiroflex.tgz,
> shiroflex.tgz, shiroflex-war-1.0-SNAPSHOT.war
>
>
> Commiters,
> I have created the following classes that I used to integrate Shiro with Flex
> AMF. I would like to contribute them to the shiro. Please let me know if
> there is interest and the procedure for doing so. I have included the class
> names with a brief description of what they do. They are currently outside of
> the Shiro code base that I checked out, but I could combine them if
> interested.
> Best Regards,
> Dave
> /* Authentication and Authorization need to let AMF Ping, Login, Logout
> messages pass through
> without processing. They call FlexMessageHelper to introspect the binary
> message to see if it is allowed to pass.
> If not, normal Authentication, and Authorization takes place.
> */
> public class FlexAuthenticationFilter extends AuthenticationFilter;
> public class FlexPermissionsAuthorizationFilter extends
> PermissionsAuthorizationFilter;
> public class FlexRolesAuthorizationFilter extends RolesAuthorizationFilter;
> /*Helper methods for introspecting the contents of the amf message. It is
> conceivable that a security handler
> might need to introspect the contents of a request. It would be nice if Shiro
> wrapped the request automatically so that anyone can read the contents without
> causing an end of stream error for a filter down the line.
> Message helper deserializes the AMF message and checks to see if it is a
> PING, LOGON, or LOGOUT request.
> */
> public class FlexHttpServletRequestWrapper extends HttpServletRequestWrapper;
> public class FlexMessageHelper;
> /* Custom Flex Login command that calls Subject.login returns a Principal
> back to Flex.
> */
> public class FlexLoginCommand implements LoginCommand;
> public class FlexPrincipal implements Principal;
--
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
