Users' maas api keys do not have a name

Bug #1536354 reported by Scott Moser
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
Wishlist
Aymen Frikha

Bug Description

i logged into a maas system where multiple have access to a single account.
looked to http://<IP>/MAAS/account/prefs/

I saw
 "You'll need a separate API key for each Juju environment."
and 6 different keys.

There is no way to know who has what key, or any purpose for such keys.
that makes revoking keys difficult.

This issue doesn't have to occur because of shared account, If i had multiple juju environments, i'd quite likely have half a dozen keys generated. If I lost some, i'd have no easy way of knowing which were to be deleted and which were still in use.

Related branches

Changed in maas:
importance: Undecided → Wishlist
status: New → Triaged
milestone: none → 2.0.0
Revision history for this message
Gavin Panella (allenap) wrote : Re: users' maas api keys should have a name

The new MAAS CLI that I'm working on allows you to log-in to MAAS with a username and password, but it does so only to obtain a new API key, thus removing the need to copy-and-paste the API key from the UI. It would be very useful to be able to add a note or comment (like "MAAS CLI / $<email address hidden>") alongside the newly minted key so it can be selectively removed later on.

summary: - users' maas api kesy should have a name
+ users' maas api keys should have a name
Gavin Panella (allenap)
summary: - users' maas api keys should have a name
+ Users' maas api keys do not have a name
Ryan Beisner (1chb1n)
tags: added: maas-shared-lab uosci
Changed in maas:
milestone: 2.0.0 → 2.1.0
Victor Tapia (vtapia)
tags: added: sts
Changed in maas:
assignee: nobody → Aymen Frikha (aym-frikha)
description: updated
Changed in maas:
status: Triaged → In Progress
Changed in maas:
status: In Progress → Fix Committed
Revision history for this message
Mike Pontillo (mpontillo) wrote :

With the fix Aymen contributed, users can now use the `maas <profile> accounts` and `maas apikey` commands to assign consumer names to key, and view keys' consumer names.

Examples: http://paste.ubuntu.com/23289946/

(Though the `apikey` command changed a little before it landed.)

There is an issue with the web UI portion, so we split it off to a separate branch. It's using the old YUI code and is more difficult for us to instruct a new contributor to develop with, since Web UI is moving to angular. (it's also questionable if we should do this, IMHO, since we'll likely replace it soon.)

Revision history for this message
Martin Pitt (pitti) wrote : Please test proposed package

Hello Scott, or anyone else affected,

Accepted maas into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/maas/2.1.0+bzr5480-0ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

tags: added: verification-needed
Revision history for this message
Andres Rodriguez (andreserl) wrote :

I've tested this and can confirm it has been fixed. Marking verification-done

tags: added: verification-done
removed: verification-needed
Changed in maas:
status: Fix Committed → Fix Released
Revision history for this message
Steve Langasek (vorlon) wrote : Update Released

The verification of the Stable Release Update for maas has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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