[aerogear-dev] AGSEC - Component planning

Bruno Oliveira bruno at abstractj.org
Thu May 23 16:34:05 EDT 2013



Jay Balunas wrote:
>
> On May 23, 2013, at 3:36 PM, Bruno Oliveira wrote:
>
>>
>>
>> Jay Balunas wrote:
>>> On May 23, 2013, at 2:45 PM, Bruno Oliveira wrote:
>>>
>> I can document it if necessary.
>
> +1, but where - in the AGSEC description section, or somewhere on in the
> docs? Perhaps in an updated version of
> http://aerogear.org/docs/guides/JIRAUsage/ ?

+1 Once this is pretty specific to AGSEC and maybe AGRAD

>
>>>
>>> Not sure of the diff with auth and authZ?
>>
>> auth - will be issues or feature requests for authentication.
>> Ex:
>>
>> - Add two-factor authentication support to JS
>> - Application X raises http 500 on login
>> - AeroGear security should provide support for captchas (meh)
>>
>> authZ - anything directly related with authorization
>> Ex:
>>
>> - Add Role-Based Authorization support on AeroGear security
>> - Even after provide the correct credentials user Homer is receiving
>> HTTP 401 response
>>
>> Makes sense?
>
> Yup, now I see what you mean. Would it be better to spell them out all
> the way then? authentication and authorization ?

+1 Agreed with you and Kris.




More information about the aerogear-dev mailing list