mgr/dashboard: Fix username validation for special characters by URL-encoding user...

When validating usernames, special characters such as '#' were not being URL-encoded before being appended to the user lookup endpoint.
Because the browser treats '#' as a URL fragment, the request path was truncated, causing the backend to return an incorrect response and the UI to display a misleading "User already exists" validation error.

Fixes: https://tracker.ceph.com/issues/77129
Signed-off-by: Aashish Sharma <aasharma@redhat.com>
(cherry picked from commit b2ed52b2a4d86ad6fa19851053badfa9118c4b6f)

diff --git a/src/pybind/mgr/dashboard/frontend/src/app/shared/api/user.service.ts b/src/pybind/mgr/dashboard/frontend/src/app/shared/api/user.service.ts
index 95c80dd4665a039cc41e67e9c162b30d43a9650a..d432e318471c5c472451dd24dad79fb4a6d0316c 100644 (file)
--- a/src/pybind/mgr/dashboard/frontend/src/app/shared/api/user.service.ts
+++ b/src/pybind/mgr/dashboard/frontend/src/app/shared/api/user.service.ts
@@ -21,7 +21,7 @@ export class UserService {
   }
 
   get(username: string) {
-    return this.http.get(`api/user/${username}`);
+    return this.http.get(`api/user/${encodeURIComponent(username)}`);
   }
 
   create(user: UserFormModel) {