Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2263529

Summary:	RFE: Following BZ#2050728, users lost the ability to re-use a username but also now hit an error message when trying to use an existing one
Product:	Red Hat OpenStack	Reporter:	David Hill <dhill>
Component:	openstack-manila	Assignee:	OpenStack Manila Bugzilla Bot <openstack-manila-bugs>
Status:	CLOSED DEFERRED	QA Contact:	Alfredo <alfrgarc>
Severity:	low	Docs Contact:	RHOS Documentation Team <rhos-docs>
Priority:	unspecified
Version:	16.2 (Train)	CC:	ashrodri, bhull, gfidente, gouthamr, rsachere, vhariria
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-12-11 16:43:45 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description David Hill 2024-02-09 14:32:25 UTC

Description of problem:
RFE: Following BZ#2050728 [1], users lost the ability to re-use a username but also now hit an error message when trying to use an existing one instead of just allowing creation.   This RFE could be a bug because behavior changed from previously working behavior (fixing security sometimes break things).   In this RFE, it would be better to allow a user to use "cloud-user" in his tenant without having an error message "cloud-user is in use" if it exists.   This can lead to username leakage by trial error as well.   The right fix here might be to create a user like "$TENANT_ID.cloud-user" in ceph auths and allow the current user to use the chosen username.   Other way around that would be to automatically generate a username like a "uuid" or a random set of letters bound to a ceph auth key.


[1] https://bugzilla.redhat.com/show_bug.cgi?id=2050728
Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Create a user in manila called "cloud-user"
2. In another tenant, try creating another "cloud-user"
3.

Actual results:
It fails

Expected results:
It should not fail or should not let people know that user is already in use.

Additional info: