*thinking* 


On Thu, Jul 31, 2014 at 9:49 AM, Bruno Oliveira <bruno@abstractj.org> wrote:
Good morning qmx,

I'm all for suggestions, server side bits made sense in the past, today
with Keycloak, not anymore.

Also, most of our security bits are covered per platform, for example AG
Crypto at iOS, JS, Cordova and Android documentation — I would like to
avoid duplication.

I'm all for an education material, not sure if we should name it
"AeroGear Security".


Learn about AeroGear's mobile security (vision?)  --> LINK TO 'SOME PAGE'

'SOME PAGE' could be a langing page, that lists the different approaches

= Mobile Client Security

AeroGear Crypto supports X,Y,Z on different platforms:
* Android (Link to the Android AG-Crypto usage page/doc)
* Apache Cordova (Link to the Cordova AG-Crypto usage page/doc)
* iOS (Link to the iOS AG-Crypto usage page/doc)

= Server Security (for Mobile Clients?)
* LINK to Keycloak (+ a refernece to the UPS?)
* Link to PicketLink? (could also include a link to the 'mobile-contacts' quickstart )



Now I wnder if we could/should also include the current OAth2 efforts of our team on such "Mobile Security" page 



-Matthias





 

On 2014-07-30, Douglas Campos wrote:
> On Wed, Jul 30, 2014 at 03:58:38PM -0300, Bruno Oliveira wrote:
> > Good morning peeps, as you know, AG Security was deprecated, but we
> > still have references on AeroGear site
> > http://staging.aerogear.org/docs/guides/aerogear-security/. Probably a
> > bad rebase, once it was already removed here:
> > https://github.com/aerogear/aerogear.org/pull/287/files ?
> >
> > Atm I'm looking for volunteers to replace this section at the main page
> > or suggestions about how to improve it. Please see: http://staging.aerogear.org.
> >
> > "Mobility and security, both
> >
> > Integrate with your existing enterprise environment. AeroGear provides
> > Two-Factor Authentication and One-Time-Password features to improve your
> > application's security.
> >
> > Learn about AeroGear Security"
> What message are we trying to convey here? Do we want to fill the void
> left by AeroGear Security with educational material (like "use keycloak
> for this") or are we going to just yank all references?
>
> >
> > Suggestions are welcome.
> >
> > --
> >
> > abstractj
> > PGP: 0x84DC9914
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev@lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> --
> qmx
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

--

abstractj
PGP: 0x84DC9914
_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf