[cap-talk] Confusing deputies with SAML assertions (was: Re: Confused Deputies in Capability Systems)
John Carlson
john.carlson3 at sbcglobal.net
Tue Feb 10 03:53:53 EST 2009
> Jed wrote:
> I use the term "capability" to refer to a representation of object
> access (access authority) that:
>
> 1. can be validated when used as authorization for a service
> request, and
>
> 2. can be communicated between any two processes that can
> communicate data.
>
> Do SAML assertions meet the above criteria (#1, #2) for
> "capabilities"?
I believe that #1 can be met with asymmetric encryption of SAML. The
capability is encrypted similar to your paper, Jed--here http://www.webstart.com/jed/papers/Managing-Domains/#s13
Whatever comes out of the encryption may be communicated between
two processes, thus #2 can be met. Recall that Alan's implementation
sends the authorization SAML to the active entity when the active
entity authenticates.
More information about the cap-talk
mailing list