Re: [aerogear-dev] AeroGear Security - Overview

On May 23, 2013, at 3:12 PM, Deepali Khushraj wrote: > > On May 23, 2013, at 3:06 PM, Deepali Khushraj <dkhushra(a)redhat.com > <mailto:dkhushra@redhat.com>> wrote: > >> >> On May 23, 2013, at 2:25 PM, Jay Balunas <jbalunas(a)redhat.com >> <mailto:jbalunas@redhat.com>> wrote: >> >>> >>> On May 23, 2013, at 10:32 AM, Deepali Khushraj wrote: >>> >>>> Thanks for the image! >>>> >>>> This picture is helpful in understanding the planned security >>>> components and dependencies on external frameworks. >>>> >>>> One aspect I'd like to understand still is are these components >>>> just REST wrappers, or will we be adding new security features as >>>> well. >>> >>> I'm not sure I understand your question. REST wrappers of what? >> >> REST API for features in the security frameworks we are using so they >> can be invoked by a mobile client. This would be VERY feature specific imo. Some may act like that and other may not. >> >>> >>>> If so, what are these features that will help the enterprise >>>> developer in securing their mobile apps. >> >> The words security and crypto, in my mind, are quite broad. I am >> trying to understand what these libs will enable developers to do. > > More specifically, on server-side, what can developers do, which they > cannot already achieve with [a] Java/Java EE security, [b] app > security frameworks like PicketLink and Shiro [c] Crypto libs. > > On client-side, what are the mobile security features which could help > with enterprise app development. I think this will become more clear as we move through the planning phase for the more advanced features. We'll be discussing this on the ML and then getting it on the site's roadmap pages. > >> >>>> >>>> On May 22, 2013, at 10:45 AM, Bruno Oliveira <bruno(a)abstractj.org >>>> <mailto:bruno@abstractj.org>> wrote: >>>> >>>>> Good morning my friends. >>>>> >>>>> One of the big question around security, is how is going to look >>>>> like with our projects growing fast. So I have the whole picture >>>>> in my mind and I'd like to share with you guys, for feedback, >>>>> tomatoes or whatever. >>>>> >>>>> The image is attached to this e-mail, but I'm not sure if we have >>>>> any filters so, here comes the gist >>>>> https://gist.github.com/abstractj/8446e5faa8d58319aeb0 >>>>> >>>>> Thanks in advance. >>>>> <secoverview.jpg>_______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev(a)lists.jboss.org <mailto:aerogear-dev@lists.jboss.org> >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev(a)lists.jboss.org <mailto:aerogear-dev@lists.jboss.org> >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev(a)lists.jboss.org <mailto:aerogear-dev@lists.jboss.org> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org <mailto:aerogear-dev@lists.jboss.org> > https://lists.jboss.org/mailman/listinfo/aerogear-dev _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev