Service users and service tenant show up in syspanel

[Tres Henry]

Now that we have accounts for each service in keystone the user UI looks like: http://i.imgur.com/Om5UT.png which seems less than ideal. Is there some field we can add that allows the UI to filter out service users?

[Jesse Andrews (anotherjesse)]

You might want them there to be able to update the user/password

[Tres Henry (tres)]

I didn't realize the service accounts might need to be managed. Maybe we can do something with the user and tenant UIs to make it clear that these are "special" objects in the system and altering or removing them will impact the health of the system?

[Gabriel Hurley (gabriel-hurley)]

Yeah. There definitely needs to be special handling here... however, step one of that is for Keystone to send back some form of identifying data so that API consumers know which Users (and which Tenants) are special.

Added note, this applies to both the service users *and* the service tenant.

[Dolph Mathews (dolph)]

Need a bit more detail on what qualifies as "special" and how to indicate that at the API level. special=true seems less than useful ;)

[David Stanek (dstanek)]

Is this still needed? If so is there any more detail about what makes an account special?

[Dolph Mathews (dolph)]

We now have containers for users (domains and external IdPs), which I think satisfies the requirement for certain users to carry a special designation (they could be owned by a service domain, for example).

[Matthias Runge (mrunge)]

still valid; horizon has still no idea about something like "service tenants"

[Akihiro Motoki (amotoki)]

Per comment #6, there is nothing to do in horizon side. Marking this as Invalid.