OpenStack Dashboard (Horizon)

Service users and service tenant show up in syspanel

Bug #948644 reported by Tres Henry on 2012-03-07

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	OpenStack Dashboard (Horizon)	Invalid	Wishlist	Unassigned
	OpenStack Identity (keystone)	Invalid	Wishlist	Unassigned

Bug Description

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?

Joseph Heck (heckj) on 2012-03-07

Changed in horizon:
status:	New → Confirmed
Changed in keystone:
status:	New → Confirmed
importance:	Undecided → Medium

Revision history for this message

Jesse Andrews (anotherjesse) wrote on 2012-03-07:

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

Revision history for this message

Tres Henry (tres) wrote on 2012-03-07:

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?

Revision history for this message

Gabriel Hurley (gabriel-hurley) wrote on 2012-03-19:

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.

summary:

- Service users show up in syspanel
+ Service users and service tenant show up in syspanel

Devin Carlen (devcamcar) on 2012-03-19

Changed in horizon:
importance:	Undecided → Medium
tags:	added: essex-rc-potential

Gabriel Hurley (gabriel-hurley) on 2012-03-20

tags:

removed: essex-rc-potential

Gabriel Hurley (gabriel-hurley) on 2012-10-02

Changed in horizon:
importance:	Medium → Wishlist

Revision history for this message

Dolph Mathews (dolph) wrote on 2013-03-06:

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 ;)

Changed in keystone:
status:	Confirmed → Incomplete

Santiago Baldassin (santiago-b-baldassin) on 2014-03-10

Changed in horizon:
assignee:	nobody → Santiago Baldassin (santiago-b-baldassin)

Santiago Baldassin (santiago-b-baldassin) on 2014-03-11

Changed in horizon:
assignee:	Santiago Baldassin (santiago-b-baldassin) → nobody

Revision history for this message

David Stanek (dstanek) wrote on 2014-05-27:

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

Revision history for this message

Dolph Mathews (dolph) wrote on 2014-05-27:

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).

Changed in keystone:
importance:	Medium → Wishlist
status:	Incomplete → Invalid

Revision history for this message

Matthias Runge (mrunge) wrote on 2015-11-24:

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

Revision history for this message

Akihiro Motoki (amotoki) wrote on 2017-09-20:

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

Changed in horizon:
status:	Confirmed → Invalid

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.