Can't set a specific API key through the API or UI

Bug #1488649 reported by Jason Hobbs
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Invalid
Wishlist
Unassigned

Bug Description

There is no way, through the API or CLI, to set an API key for a user to specific value. I'm setting up a new MAAS to replace an existing MAAS server. I want to reuse the MAAS API keys from my existing MAAS server so I don't have to redistribute new API keys to all my infrastructure that uses it.

To work around this, I wrote a script that used sql directly to set the key values in the piston_consumer and piston_token tables in the database.

This was with MAAS 1.8.2.

Tags: oil
summary: - Can't set a specific API key through the API
+ Can't set a specific API key through the API or UI
Revision history for this message
Andres Rodriguez (andreserl) wrote :

It is my understanding that by design, the API is to be generated automatically by MAAS and not allow the user to change that or specify one themselves. That being said, I don't know if we would like to support this in the future, but at the moment it is nto something that has priority.

Changed in maas:
status: New → Invalid
status: Invalid → Triaged
importance: Undecided → Low
importance: Low → Wishlist
milestone: none → next
Revision history for this message
Blake Rouse (blake-rouse) wrote :

Yeah this seems like it could be a security issue. Don't really like this idea at all. It would just as simple to update the API key on the caller.

Revision history for this message
Blake Rouse (blake-rouse) wrote :

I am "+1" for marking this "Won't fix."

Revision history for this message
Jason Hobbs (jason-hobbs) wrote :

Why would it be a security issue? It's not just as simple to update on the caller - the caller is in multiple places, MAAS is just in one.

Revision history for this message
Adam Collard (adam-collard) wrote :

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team

Changed in maas:
status: Triaged → Invalid
Changed in maas:
milestone: next → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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