On 01/04/2011 11:15 AM, Perry Myers wrote:
On 01/04/2011 11:12 AM, Ted Ross wrote:
> On 01/03/2011 09:47 AM, Perry Myers wrote:
>> Ted,
>>
>> I know we've had this discussion before, but wanted to triple check on
>> this because a lot of the Matahari model depends on it.
>>
>> My understand is that it is possible to restrict what role a connection
>> to a broker is able to take via auth credentials. For example:
>>
>> * broker1 has two auth credentials defined:
>> - user foo: allows connections from both QMF Consoles and QMF Agents
>> - user bar: allows connections only from QMF Agents
>>
>> With this functionality, we could provide a single broker and only give
>> out user foo credentials to Consoles running in protected areas (mgmt
>> DMZ for example). And then only provide user bar credentials to the
>> guests running in the Cloud so they could only ever connect to the
>> external broker as an Agent.
>>
>> Can you please confirm this?
>>
>> Thanks!
>>
>> Perry
> Perry,
>
> Yes, this is correct. To be more precise, Qpid uses role-based ACLs where
> auth identities are mapped to a role which then has specific access
> rights. One feature we talked about was mapping transports to roles. This
> is applicable to the virtio-serial scenario where the role could be
> assigned based on the fact that the client is on a guest VM (without the
> need for provisioning credentials to the guest).
>
> I will write up an architectural description of how this works to provide
> greater detail.
Excellent, thanks!
Ted,
If you could also provide a note on the use of domains with the new API,
as that is how
we will secure the config agent updates.
Carl.