You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The SOL (Serial Over LAN) console button is currently visible to all users on the Overview screen, regardless of their privilege level. This can lead to unauthorized access to the SOL console.
To Reproduce Steps to reproduce the behavior:
Log in to the system with a user account that does not have the necessary privileges for accessing the SOL console (privilege role of operator or read only).
Navigate to the 'Overview' screen.
Observe that the SOL console button is visible and accessible.
Expected behavior
The SOL console button should be conditionally rendered in the Overview page based on user privilege. Only users with the appropriate permissions should see and access this button. This ensures that unauthorized users cannot access the SOL console functionality.
Screenshots
Additional context
This bug affects the visibility of the SOL console button in the OverviewQuickLinks component. Proper privilege checks should be implemented to control access to this functionality.
The text was updated successfully, but these errors were encountered:
Describe the bug
The SOL (Serial Over LAN) console button is currently visible to all users on the Overview screen, regardless of their privilege level. This can lead to unauthorized access to the SOL console.
To Reproduce Steps to reproduce the behavior:
Expected behavior
The SOL console button should be conditionally rendered in the Overview page based on user privilege. Only users with the appropriate permissions should see and access this button. This ensures that unauthorized users cannot access the SOL console functionality.
Screenshots
Additional context
This bug affects the visibility of the SOL console button in the OverviewQuickLinks component. Proper privilege checks should be implemented to control access to this functionality.
The text was updated successfully, but these errors were encountered: