Issue #4313
closed
Username is mutable and can be updated/changed via REST API
Status:
CLOSED - CURRENTRELEASE
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
- Triaged changed from No to Yes
- Sprint set to Sprint 47
- Tags Easy Fix, Pulp 3 RC Blocker added
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.
- Related to Task #2635: Determine which fields are mutable on each resource. added
- Status changed from NEW to ASSIGNED
- Assignee set to ttereshc
- Status changed from ASSIGNED to POST
- Status changed from POST to MODIFIED
- Copied to Test #4360: Username is mutable and can be updated/changed via REST API added
- Related to Task #4398: Remove "User" REST API calls added
- Sprint/Milestone set to 3.0.0
- Tags deleted (
Pulp 3, Pulp 3 RC Blocker)
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Also available in: Atom
PDF
.
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