MongoDB Authentication
Security hardening for NMIS and OMK found the following findings
A single identity (username and password) was used for NMIS and all OMK products:
Username | Role | Used by | Password |
|---|---|---|---|
| the pre-NMIS 9.7.0 shared identity, | NMIS and every other OMK product on the host | op42Flow42 |
The solution is to implement the following policies:
least privilege principle
separate identities for each product
no shared secrets
From NMIS 9.7.0 the following identities are used:
Username | Role | Used by | Password |
|---|---|---|---|
|
| nothing at runtime; bootstrap and administration only | generated, stored in the handoff file |
|
| NMIS at runtime | generated, stored in |
|
| bootstrap and administration only |
|
|
| the OMK apps at runtime |
|
| the pre-NMIS 9.7.0 shared identity, | left exactly as found; nothing removes it |
|