...
The configurations can work for both NMIS and OMK, but is a requisite that SSO is configured first.
Supported Versions
NMIS 8.7.2
opCharts 3.5.1
opEvents 2.6.3
opConfig 3.5.2
opHA 2.2.1
- opReports 3.4.2?
Limit the number of concurrent user sessions
...
if USERNAME = ALL, it will clean the sessions for all the users.
...
Lock a user not logged in certain period of time
It is possible to block lock a user if has not logged in for a specified period of time. For example, when set to 3 months, the system will lock an user is that has not logged in in the last 3 months.
...
The number of max sessions can be changed by per user.
| Code Block |
|---|
'nmis' => {
'admission' => 'true',
'groups' => 'all',
'privilege' => 'administrator',
'user' => 'nmis'
'expire_after' => 86400 * 30
}, |
...
Please, make sure opHA user has set max_sessions to 0 and expire_after in order to work properly, as opHA does not use that cookie information:
| Code Block |
|---|
'omkapi' => {
'user' => 'omkapi',
'groups' => 'all',
'privilege' => 'operator',
'max_sessions' => 0,
'expire_after' => 0
}, |
opReports: Node report does not show Node graphics
Please, make sure omk/conf/opCommon.nmis nmis_host_base and nmis8/conf/Config.nmis nis_host are properly set up.