Issue #4313
closed
Username is mutable and can be updated/changed via REST API
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
Updated by CodeHeeler almost 6 years ago
- Triaged changed from No to Yes
- Sprint set to Sprint 47
- Tags Easy Fix, Pulp 3 RC Blocker added
Updated by amacdona@redhat.com almost 6 years 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.
Updated by ttereshc almost 6 years ago
- Related to Task #2635: Determine which fields are mutable on each resource. added
Updated by ttereshc almost 6 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to ttereshc
Updated by ttereshc almost 6 years 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.
Added by ttereshc almost 6 years ago
Added by ttereshc almost 6 years ago
Revision 17f50802 | View on GitHub
Disallow user creation/update
One admin user will exist until the full support for user management is added
Updated by ttereshc almost 6 years ago
- Status changed from POST to MODIFIED
Applied in changeset pulp|17f508020abeaedb1bed949b55157be7a01fb4ec.
Updated by bherring almost 6 years ago
- Copied to Test #4360: Username is mutable and can be updated/changed via REST API added
Updated by kersom almost 6 years ago
- Related to Task #4398: Remove "User" REST API calls added
Updated by bmbouter about 5 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
.
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