summaryrefslogtreecommitdiff
path: root/src/router
diff options
context:
space:
mode:
authorPaul Fertser <fercerpav@gmail.com>2024-04-11 13:51:41 +0300
committerPaul Fertser <fercerpav@gmail.com>2024-05-02 16:32:56 +0300
commit2b33526c41c23217365e8eb0523d182bcdee622a (patch)
tree41cd050f735ccbc7503b1a8660b98d15f4ac8456 /src/router
parent01492c3dcbdba6b463ecef63f4c769520432d829 (diff)
downloadwebui-vue-2b33526c41c23217365e8eb0523d182bcdee622a.tar.xz
Allow to log in when using remote authentication
For accounts authenticated remotely (e.g. with LDAP or RADIUS) the API endpoint (handled by bmcweb) can not provide any information about RoleId currently, reporting 404 instead. This confuses the frontend and it doesn't allow to navigate at all. Fix this by lifting all frontend-side restrictions by assuming 'Administrator' role in this case. Since the backend verifies validity of each and every request anyway this doesn't affect security anyhow. Tested: logging in, out and incorrectly using local BMC and remote LDAP users, reloading the page with an active session. In all cases frontend behaved as expected, storing assumed RoleId after getting 404 not found reply and using it for unrestricted routing decisions. Change-Id: If17d06bf0b8a372acd1980f6777227e25d9c78d8 Signed-off-by: Paul Fertser <fercerpav@gmail.com>
Diffstat (limited to 'src/router')
-rw-r--r--src/router/routes.js2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/router/routes.js b/src/router/routes.js
index eb376aad..5424cab8 100644
--- a/src/router/routes.js
+++ b/src/router/routes.js
@@ -301,4 +301,4 @@ const routes = [
},
];
-export default routes;
+export { routes as default, roles };