10:49 a.m.
Hi guys,
I've created a wiki entry for fine-grained authorization. Please look at it:
https://github.com/infinispan/infinispan/wiki/Fine-grained-security-for-c...
And let me know your thoughts. Personally I'm not sure the second case
is worth the effort, but it definitely has its advantages.
Tristan
--
Tristan Tarrant
Infinispan Lead
JBoss, a division of Red Hat
2:25 p.m.
Unless there is a big push for ACLs from users, I think we should
stick to the callback version.
Cheers
Dan
On Tue, Sep 15, 2015 at 11:49 AM, Tristan Tarrant <ttarrant(a)redhat.com> wrote:
Hi guys,
I've created a wiki entry for fine-grained authorization. Please look at it:
https://github.com/infinispan/infinispan/wiki/Fine-grained-security-for-c...
And let me know your thoughts. Personally I'm not sure the second case
is worth the effort, but it definitely has its advantages.
Tristan
--
Tristan Tarrant
Infinispan Lead
JBoss, a division of Red Hat
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
3:11 p.m.
From the perspective of liking to control things, I agree on the
callback
version. The callback implementation also seems like it will be much
easier to implement and maintain as well :) Guessing we can put everything
in SecureCache as well then.
- Will
On Tue, Sep 15, 2015 at 8:26 AM Dan Berindei <dan.berindei(a)gmail.com> wrote:
Unless there is a big push for ACLs from users, I think we should
stick to the callback version.
Cheers
Dan
On Tue, Sep 15, 2015 at 11:49 AM, Tristan Tarrant <ttarrant(a)redhat.com>
wrote:
> Hi guys,
> I've created a wiki entry for fine-grained authorization. Please look at
it:
>
>
https://github.com/infinispan/infinispan/wiki/Fine-grained-security-for-c...
>
> And let me know your thoughts. Personally I'm not sure the second case
> is worth the effort, but it definitely has its advantages.
>
> Tristan
> --
> Tristan Tarrant
> Infinispan Lead
> JBoss, a division of Red Hat
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
5:16 p.m.
Hi,
I've created a wiki entry for fine-grained authorization.
could you specify use-cases which you'd like to solve by this feature? If I
want e.g. restrict access to entries only to user who created the entry, the
callback itself doesn't easily (*) solve the problem, as I need some
additional entry metadata for the decision, etc.
Btw: in case of auth. callback I see custom code as an advantage, as it gives
me freedom to implement my security policy as I like. And we can provide some
common callbacks for users who don't want to implement it themselves.
Thanks
Vojta
(*) I can probably e.g. encode some subject hash into the key and then
allow/reject request for entry based on hash of requesting subject, but this
is not a very nice solution
3196
days inactive
3196
days old
infinispan-dev@lists.jboss.org
3 comments
4 participants
participants (4)
-
Dan Berindei -
Tristan Tarrant -
Vojtech Juranek -
William Burns