Yes, I believe there is something interesting to be done here. Jerome and I have had a couple of email exchanges and he has rightly questioned how we will address the lack of UI for each of these mechanisms. Once we close down on this release we need to identify specific usecase/flows where this will make sense.
I believe that there are usecases that aren't possible today because of the lack of this sort of identity federation in Hadoop but we will need to determine a few particular scenarios such as webapp to Hadoop cluster where the webapp has authenticated the user (perhaps via CAS) and issued a SAML assertion based SSO token, etc. It would be great to hear some of these sorts of requirements from others in the community. @umesh? Again, as we close down on this release, we need to drill into these usecases more diligently. thanks, --larry On Thu, Sep 26, 2013 at 11:46 PM, Dilli Arumugam <[email protected]>wrote: > Thanks Larry, Kevin for the pointer. > They would be a big help for us. > Dilli > > > On Thu, Sep 26, 2013 at 7:26 PM, larry mccay <[email protected]> > wrote: > > > Adding Jérôme <https://plus.google.com/u/0/115400609119053480752?prsrc=4 > > >... > > > > > > On Thu, Sep 26, 2013 at 10:22 PM, Kevin Minder < > > [email protected] > > > wrote: > > > > > Hi Everyone, > > > Larry dig this site up that has a bunch of Shiro authentication > plugins. > > > https://github.com/bujiio/**buji-pac4j< > > https://github.com/bujiio/buji-pac4j> > > > There are ASL2 based so at some point we should take a look at how we > > > might leverage them. > > > Kevin. > > > > > > -- > > > CONFIDENTIALITY NOTICE > > > NOTICE: This message is intended for the use of the individual or > entity > > > to which it is addressed and may contain information that is > > confidential, > > > privileged and exempt from disclosure under applicable law. If the > reader > > > of this message is not the intended recipient, you are hereby notified > > that > > > any printing, copying, dissemination, distribution, disclosure or > > > forwarding of this communication is strictly prohibited. If you have > > > received this communication in error, please contact the sender > > immediately > > > and delete it from your system. Thank You. > > > > > > > -- > CONFIDENTIALITY NOTICE > NOTICE: This message is intended for the use of the individual or entity to > which it is addressed and may contain information that is confidential, > privileged and exempt from disclosure under applicable law. If the reader > of this message is not the intended recipient, you are hereby notified that > any printing, copying, dissemination, distribution, disclosure or > forwarding of this communication is strictly prohibited. If you have > received this communication in error, please contact the sender immediately > and delete it from your system. Thank You. >
