Custom Login doesnt appear to work, corporate compliance requirements.
Posted: Thu May 02, 2024 8:24 am
We are implementing nagiosxi and currently have version 2024R1.1.2.
Our compliance, security and support teams are requiring some specific changes to the login screen. We see where there is a component to add customized login, but it does not see to work. even putting simple text such as "TEST" does not show.
we are happy to do our own code, but how to get it to pick it up?
some requirements:
- Legal disclaimer test
- removal of Nagios Logo, addition of our own
- remove all "contact" sale, support etc.
We are pushing this instead of their "preferred tool" which is SCOM.. If i can't make these changes, they will use it as an excuse to kill this project. We are paying for the software with support (1000+ systems), just waiting on procurement, but this battle drags on.
edit - i did see some posts that talked about it not being supported, or requiring to use a custom CSS to change the screen, but it seems that this method is a hacked up (security by obscurity??) way to do it really.. I looking for something server side to prevent to elements from going to the browser at all..
edit2 - yes we get that we might get burned on an update... we need to get this approved then fight through that..
-- Chris
Our compliance, security and support teams are requiring some specific changes to the login screen. We see where there is a component to add customized login, but it does not see to work. even putting simple text such as "TEST" does not show.
we are happy to do our own code, but how to get it to pick it up?
some requirements:
- Legal disclaimer test
- removal of Nagios Logo, addition of our own
- remove all "contact" sale, support etc.
We are pushing this instead of their "preferred tool" which is SCOM.. If i can't make these changes, they will use it as an excuse to kill this project. We are paying for the software with support (1000+ systems), just waiting on procurement, but this battle drags on.
edit - i did see some posts that talked about it not being supported, or requiring to use a custom CSS to change the screen, but it seems that this method is a hacked up (security by obscurity??) way to do it really.. I looking for something server side to prevent to elements from going to the browser at all..
edit2 - yes we get that we might get burned on an update... we need to get this approved then fight through that..
-- Chris