[
https://issues.apache.org/jira/browse/SHIRO-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12867883#action_12867883
]
Bryan Turner commented on SHIRO-160:
------------------------------------
I was thinking it may get setup as three modules:
Package: org.apache.shiro.amf
Project: support/amf
This would contain classes which do not depend any classes or interfaces which
are outside Shiro and the JDK
Package: org.apache.shiro.amf.blazeds
Project: support/amf/blazeds
Contains classes which rely on BlazeDS as an AMF provider
Package: org.apache.shiro.amf.graniteds
Project: support/amf/graniteds
Contains classes which rely on GraniteDS as an AMF provider
When I referred to reuse, I meant reusing portions of your code to build the
GraniteDS integration. The Maven poms for the support/amf/blazeds and
support/amf/graniteds will depend on BlazeDS and GraniteDS respectively, but
support/amf can't depend on either or users of one integration would have to
set up exclusions when adding a dependency. As a result, none of the flex.*
packages can be referred to in support/amf because doing so would require a
dependency in Shiro's build for a specific technology. We could twiddle with
scopes, potentially using something like external or provided, but I'd imagine
if you looked at Granite's versions of those "same" files, you'd find they're
not the same at all.
> 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
>
> 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.
-
You can reply to this email to add a comment to the issue online.
