Comment 16 for bug 1299146

So reading #12 it seems that id is the way to go - usability be damned. But I'm confused on the syntax with the double ids?

If we wanted to try and keep names, something like domain:project or domain:user would probably uniquely identify the tenant_id or user_id today - but it'll break down once Keystone adds super-conglomerates or universes concepts above domains.

But as long as you get in one id - that should be enough right?

Does an identifier like tenant_id:user_id even make sense if the user_id matches by the tenant_id doesn't? Shouldn't tenant_id:name be good enough to identify a unique user or even just user_id?