Project

Profile

Help

Issue #4313

Username is mutable and can be updated/changed via REST API

Added by ttereshc 9 months ago. Updated 6 months ago.

Status:
MODIFIED
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
Start date:
Due date:
Severity:
2. Medium
Version:
Platform Release:
Blocks Release:
OS:
Backwards Incompatible:
No
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Easy Fix
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:
Sprint 47

Description

Username is mutable and can be updated/changed via REST API.
Is it on purpose? Do we rely anywhere on username?

Suggestion: make it immutable for now


Related issues

Related to Pulp - Task #2635: Determine which fields are mutable on each resource. CLOSED - COMPLETE Actions
Related to Pulp - Task #4398: Remove "User" REST API calls MODIFIED Actions
Copied to Pulp - Test #4360: Username is mutable and can be updated/changed via REST API CLOSED - COMPLETE Actions

Associated revisions

Revision 17f50802 View on GitHub
Added by ttereshc 9 months ago

Disallow user creation/update

One admin user will exist until the full support for user
management is added

closes #4313
https://pulp.plan.io/issues/4313

Revision 17f50802 View on GitHub
Added by ttereshc 9 months ago

Disallow user creation/update

One admin user will exist until the full support for user
management is added

closes #4313
https://pulp.plan.io/issues/4313

History

#1 Updated by CodeHeeler 9 months ago

  • Triaged changed from No to Yes
  • Sprint set to Sprint 47
  • Tags Easy Fix, Pulp 3 RC Blocker added

#2 Updated by amacdona@redhat.com 9 months ago

Since we don't really have a full design for how users should work, I think we should remove the create & update mixins from the viewset, leaving a single "admin" user that is immutable.

This isn't at all what we want eventually, but it puts us in a great position to do whatever we need to in a backwards compatible way.

#3 Updated by ttereshc 9 months ago

  • Related to Task #2635: Determine which fields are mutable on each resource. added

#4 Updated by ttereshc 9 months ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to ttereshc

#5 Updated by ttereshc 9 months ago

  • Status changed from ASSIGNED to POST

https://github.com/pulp/pulp/pull/3829

@amacdona, I like the idea of disallowing user creation/update at this point.

#6 Updated by ttereshc 9 months ago

  • Status changed from POST to MODIFIED

#7 Updated by bherring 9 months ago

  • Copied to Test #4360: Username is mutable and can be updated/changed via REST API added

#8 Updated by kersom 8 months ago

  • Related to Task #4398: Remove "User" REST API calls added

#9 Updated by daviddavis 6 months ago

  • Sprint/Milestone set to 3.0

#10 Updated by bmbouter 6 months ago

  • Tags deleted (Pulp 3, Pulp 3 RC Blocker)

Please register to edit this issue

Also available in: Atom PDF