I'd say that finding ready-made suitable accounting solution for
OpenTox is almost impossible. We have seen that even just AA presents
significant challenge because of the specifics of our data that need
to be protected. So, if we really want to have quotas implemented,
that almost certainly means we need to develop the system to handle
them.

Cheers,
Luchesar


On Tue, Jun 15, 2010 at 14:31, Andreas Maunz <andreas at maunz.de> wrote:
> Nina Jeliazkova wrote on 06/15/2010 01:19 PM:
>>>>>
>>>>> 3. Every user should be allowed to make use of a pre-specified fraction
>>>>> of the server's storage capacity which simply means that there should
>>>>> be
>>>>> an upper bound on the number of models a user can create (say 50000 or
>>>>> something like that). How can such a constraint be established using
>>>>> policies?
>>>>>
>>>> Quota support is something we had not yet discussed, but it is indeed
>>>> important.
>>>>
>>>
>>> Is there some perspective of accomplishing this kind of authorization
>>> using SSO or web services should take that on?
>>>
>> This is actually accounting, not authorisation, and we hadn't considered
>> it at all.   I am slightly in favour of separating accounting from
>> services.
>>
>> Andreas, what do you think?  Does OpenSSO provide a solution for AAA ?
>
> No, I don't think it does. OpenSSO is originally designed to have a single
> administrator for managing policies and not for different users creating
> their individual policy (although this is in the pipeline of development at
> the moment). Therefore, the aspect of controlling the number of policies has
> been neglected.
> Other aspects of accounting (e.g. failed attempts to authenticate) are
> explicitly covered by a special logging service, but I don't think quota is.
>
> Regards
> Andreas
> _______________________________________________
> Development mailing list
> Development at opentox.org
> http://www.opentox.org/mailman/listinfo/development
>