[aerogear-dev] AGSEC - Component planning

[Jay Balunas]

This looks good to me, especially for the initial set.

On May 23, 2013, at 4:36 PM, Bruno Oliveira wrote:

> Thanks Kris.
> 
> Here comes the update list of suggested components for AGSEC:
> 
> - examples: demos, example of usage, snippets
> - docs: documentation about how to make use of security libraries, blog 
> posts, updates on aerogear.org
> - CI: updates on CI like new jobs to be created or improvements
> - OTP: TOTP & HOTP components which affects the server, iOS, Android and JS
> - crypto: implementations of cryptographic algorithms to support 
> server/client side
> - security-*: aerogear-security, aerogear-security-picketlink and 
> aerogear-security-shiro.
> - social: Twitter, Facebook, Google (any social networks to share your 
> password with friends)
> - authentication: authentication methods to be provided (Basic, Digest, 
> LDAP, OAuth2, Hawk, Mozilla Persona, Two-factor)
> - authorization: authorization methods to be implemented or supported.
> - storage: issues and features related with encrypted storage
> - cache: issues and features related with encrypted cache
> - openshift: for examples on OpenShift and eventual issues
> - testing: For the efforts leaded by Karel.
> 
> Kris Borchers wrote:
>>> Yup, now I see what you mean.  Would it be better to spell them out
>>> all the way then?  authentication and authorization ?
>> 
>> +1 - It's not obvious what authZ is at a glance.
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev