openstack team mailing list archive

[Dolph Mathews <dolph.mathews@xxxxxxxxx>]

That's correct. Right now, all endpoints registered in keystone are
returned to all users, regardless of whether they actually have any sort of
authorization on those endpoints.

I suspect we'll be having a planning session at the design summit on this
topic -- I'd be helpful to better understand your ideal use case in
suppressing endpoints from the catalog? In Grizzly, users, groups,
projects, and domains have absolutely no relationship with services and
endpoints within keystone. That becomes deployment specific when you
consider how RBAC is applied service-side with policy.json, etc, but those
services are not necessarily aware of how they appear in the service
catalog, nor does keystone interpret policy files other than it's own.


-Dolph


On Mon, Mar 4, 2013 at 2:32 PM, Miller, Mark M (EB SW Cloud - R&D -
Corvallis) <mark.m.miller@xxxxxx> wrote:

>  Hello,****
>
> ** **
>
> I have been looking over the Keystone v3 API documentation as well as the
> database table columns. My question concerns endpoint access restrictions.
> I don’t see any noticeable way to associate endpoints with domains which
> means that any user can access any endpoint of any domain. Is this correct?
> The only database column that might come into play is the region column of
> the endpoint table.****
>
> ** **
>
> Regards,****
>
> ** **
>
> Mark Miller****
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>