shiro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kalle Korhonen <kalle.o.korho...@gmail.com>
Subject Re: open items for shiro 2.0
Date Wed, 05 Aug 2015 21:33:15 GMT
On Wed, Aug 5, 2015 at 7:51 AM, jleleu <leleuj@gmail.com> wrote:

> I'd like to propose to replace the CAS support (shiro-cas module) by a new
> shiro-pac4j module which supports the CAS, SAML, OpenID (Connect), OAuth
> and Google App Engine mechanisms. It would be a revamp of the buji-pac4j
> extension which is widely used and maintained for years. The CAS support
> available in buji-pac4j is ahead of the official one in Shiro (proxy
> support).
>

Instead of replacing, it might be better that we simply remove cas support
in the core and recommend your module instead. There are way too many
integrations that we could bring in but maintaining multiple ones slows
down development of the core offering.

Kalle


>
> I'd also like to propose to think about refactoring the login computation
> (the getLoginUrl() method) into some pluggable component. Currently, for
> the buji-pac4j extension, I have a custom behaviour to compute the login
> url and I need to subclass all filters to implement it (
>
> https://github.com/bujiio/buji-pac4j/tree/master/servlet/src/main/java/io/buji/pac4j/filter
> ).
>
> Thanks.
> Best regards,
> Jérôme
>
>
>
> 2015-08-05 14:26 GMT+02:00 Darin Gordon [via Shiro Developer] <
> ml-node+s582600n7578730h90@n2.nabble.com>:
>
> > There's a major shiro v2 deliverable pending for support of authorization
> > in the AccountStoreRealm.  Is anyone working on its implementation, or at
> > least mulling over a design?
> >
> > As to the direction that shiro v2 is heading with support for
> > authorization, the solution seems intuitive enough to guess what
> > will/should be done.
> >
> > I'll be submitting a proposal shortly should anyone not respond!
> >
> > -DG-
> >
> >
> >
> >
> > On Wed, Aug 5, 2015 at 6:33 AM, Darin Gordon <[hidden email]
> > <http:///user/SendEmail.jtp?type=node&node=7578730&i=0>> wrote:
> >
> > > Thanks Les.  The v2 work that was already done to support event-driven
> > > communication and migrate to use of the Account-based model is
> > significant
> > > progress towards the v2 goals.  Have you considered phasing release of
> > > these TBD's?
> > >
> > > in re:
> > >
> > > event-driven design, I assume the pending work is related to
> > > authorization-based events.  Is there any other work in mind?
> > >
> > > realm refactoring:  the AccountStoreRealm is a major departure from the
> > > prior Realm model.  What aside from that which has been already
> > implemented
> > > for v2 with respects to support for the Account model requires
> > > implementation?
> > >
> > >
> > > TBD
> > >
> > >    - Remove the usage of the word Principal
> > >    <
> >
> https://cwiki.apache.org/confluence/display/SHIRO/Version+2+Brainstorming#Version2Brainstorming-RemovetheusageofthewordPrincipal
> >
> >
> > >    - Rename AuthenticationInfo to Account
> > >    <
> >
> https://cwiki.apache.org/confluence/display/SHIRO/Version+2+Brainstorming#Version2Brainstorming-RenameAuthenticationInfotoAccount
> >
> >
> > >    - Split shiro-core into modules
> > >    - Event-driven design
> > >
> > >
> > >    - Subject PrincipalCollection
> > >    - Component Names
> > >    -
> > >    - Authorization ANTLR Grammar
> > >    <
> >
> https://cwiki.apache.org/confluence/display/SHIRO/Version+2+Brainstorming#Version2Brainstorming-AuthorizationANTLRGrammar
> >
> >
> > >    - AuthorizationRequest/Response
> > >    <
> >
> https://cwiki.apache.org/confluence/display/SHIRO/Version+2+Brainstorming#Version2Brainstorming-AuthorizationRequest/Response
> >
> >
> > >    - Multi-Stage Authentication via request/response
> > >    <
> >
> https://cwiki.apache.org/confluence/display/SHIRO/Version+2+Brainstorming#Version2Brainstorming-Multi-StageAuthenticationviarequest/response
> >
> >
> > >    -
> > >    - Reinforce customization via OO Delegation (composition over
> > >    inheritance)
> > >    <
> >
> https://cwiki.apache.org/confluence/display/SHIRO/Version+2+Brainstorming#Version2Brainstorming-ReinforcecustomizationviaOODelegation(compositionoverinheritance)
> >
> >
> > >    - Captcha Support
> > >    <
> >
> https://cwiki.apache.org/confluence/display/SHIRO/Version+2+Brainstorming#Version2Brainstorming-CaptchaSupport
> >
> >
> > >    - Configuration per filter instance and no path matching
> > >    <
> >
> https://cwiki.apache.org/confluence/display/SHIRO/Version+2+Brainstorming#Version2Brainstorming-Configurationperfilterinstanceandnopathmatching
> >
> >
> > >    - Web module repackaging.
> > >    <
> >
> https://cwiki.apache.org/confluence/display/SHIRO/Version+2+Brainstorming#Version2Brainstorming-Webmodulerepackaging
> .>
> >
> > >
> > >
> > > Implemented
> > >
> > >    - Realm refactoring
> > >    <
> >
> https://cwiki.apache.org/confluence/display/SHIRO/Version+2+Brainstorming#Version2Brainstorming-Realmrefactoring
> >
> >
> > >
> > >                - AccountStoreRealm implemented
> > >
> > >
> > >    - Event-driven design
> > >    <
> >
> https://cwiki.apache.org/confluence/display/SHIRO/Version+2+Brainstorming#Version2Brainstorming-Event-drivendesign
> >
> >
> > >
> > >                - /event sub-package implemented
> > >                - Authentication-based event communication implemented
> > >
> > >
> > > On Tue, Aug 4, 2015 at 4:17 PM, Les Hazlewood <[hidden email]
> > <http:///user/SendEmail.jtp?type=node&node=7578730&i=1>> wrote:
> > >
> > >> This is what we currently have - edits are welcome:
> > >>
> > >>
> >
> https://cwiki.apache.org/confluence/display/SHIRO/Version+2+Brainstorming
> > >>
> > >> --
> > >> Les
> > >>
> > >> On Tue, Aug 4, 2015 at 12:52 PM, Darin Gordon <[hidden email]
> > <http:///user/SendEmail.jtp?type=node&node=7578730&i=2>> wrote:
> > >>
> > >> > Is there a project plan for 2.0?   I'd like to understand what the
> > >> > remaining deliverables are.
> > >> >
> > >> > Thanks!
> > >> >
> > >> > DG
> > >> >
> > >>
> > >
> > >
> >
> >
> > ------------------------------
> > If you reply to this email, your message will be added to the discussion
> > below:
> >
> >
> http://shiro-developer.582600.n2.nabble.com/open-items-for-shiro-2-0-tp7578720p7578730.html
> > To start a new topic under Shiro Developer, email
> > ml-node+s582600n582600h60@n2.nabble.com
> > To unsubscribe from Shiro Developer, click here
> > <
> http://shiro-developer.582600.n2.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=582600&code=bGVsZXVqQGdtYWlsLmNvbXw1ODI2MDB8LTExNzY2MzcxMTY=
> >
> > .
> > NAML
> > <
> http://shiro-developer.582600.n2.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
> >
> >
>
>
>
>
> --
> View this message in context:
> http://shiro-developer.582600.n2.nabble.com/open-items-for-shiro-2-0-tp7578720p7578736.html
> Sent from the Shiro Developer mailing list archive at Nabble.com.
>

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