[sakai2-tcc] Hybrid and 2.10

[Sam Ottenhoff]

Yes, I left kernel/TrustedLoginFilter untouched.  If I removed anything in
the login project that you think should remain, let me know.

--Sam


On Tue, Sep 10, 2013 at 7:01 AM, Aaron Zeckoski <azeckoski at unicon.net>wrote:

> If you mean TrustedLoginFilter I believe we are keeping that.
> Hybrid is already removed at this point.
> -AZ
>
>
> On Mon, Sep 9, 2013 at 10:04 PM, John Bush <jbush at anisakai.com> wrote:
> > If no one has a strong feeling one way or the other, I'd prefer we
> > keep this one.  This is actually a handy way to be able to pair
> > systems and do logins.  We used it once in a non-hybrid world for
> > integration with a system other than oae.
> >
> > On Mon, Sep 9, 2013 at 10:01 AM, Sam Ottenhoff <ottenhoff at longsight.com>
> wrote:
> >> I am attempting to remove these items now from trunk.  Does anyone know
> if
> >> kernel/api/src/main/java/org/sakaiproject/util/TrustedLoginFilter.java
> is
> >> still needed in a post-hybrid world?
> >>
> >>
> >> On Fri, Sep 6, 2013 at 4:27 AM, Jean-Francois Leveque
> >> <jean-francois.leveque at upmc.fr> wrote:
> >>>
> >>> I don't mind doing the work. Just to be sure, here's what I think this
> >>> means:
> >>> - remove it from trunk .externals and pom.xml. (as Sam wrote)
> >>> - remove
> >>>
> >>>
> login/login-tool/tool/src/test/org/sakaiproject/login/filter/NakamuraAuthenticationFilterTest.java
> >>> - remove
> >>>
> >>>
> login/login-tool/tool/src/java/org/sakaiproject/login/filter/NakamuraAuthenticationFilter.java
> >>> - remove providers/hybrid
> >>>
> >>> This works for my 2.8 build so I think it won't break trunk.
> >>>
> >>> How do we communicate about this?
> >>>
> >>> J-F
> >>>
> >>> On 06/09/2013 01:55, Charles Severance wrote:
> >>> >
> >>> > On Sep 5, 2013, at 7:10 PM, Steve Swinsburg <
> steve.swinsburg at gmail.com
> >>> > <mailto:steve.swinsburg at gmail.com>> wrote:
> >>> >
> >>> >> Correct, this is for one of the older OAE code bases. Pull it. The
> >>> >> code will be in SVN if people want to resurrect it or out it in
> their
> >>> >> own installs, but there is no need to continue to include deprecated
> >>> >> and unused code in the CLE.
> >>> >
> >>> > At this point it is not maintained, not testable, and effectively a
> >>> > security hole waiting to happen if we just leave the latent untested,
> >>> > unreviewed, and unmaintained code lying around on all the Sakai
> >>> > production servers in the world.
> >>> >
> >>> > It is easily resurrected if the need arises.
> >>> >
> >>> > /Chuck
> >>> _______________________________________________
> >>> sakai2-tcc mailing list
> >>> sakai2-tcc at collab.sakaiproject.org
> >>> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
> >>
> >>
> >>
> >> _______________________________________________
> >> sakai2-tcc mailing list
> >> sakai2-tcc at collab.sakaiproject.org
> >> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
> >>
> >
> >
> >
> > --
> > John Bush
> > 602-490-0470
> >
> > ** This message is neither private nor confidential in fact the US
> > government is storing it in a warehouse located in Utah for future
> > data mining use cases should they arise. **
> > _______________________________________________
> > sakai2-tcc mailing list
> > sakai2-tcc at collab.sakaiproject.org
> > http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
>
>
>
> --
> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai2-tcc/attachments/20130910/e183e206/attachment.html