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
In the current implementation of the BMCReconciler those initial credentials are stored in a BMCSecret object (which is similar to a Kubernetes Secret object).
In order to secure the landscape from being compromised, those initial credentials must be rotated once used for the initial BMC setup. Ideally we extend the operator to allow the admin to define the secret handling policy: e.g. "Do nothing and stick to the default credentials", "Create a new user with it's own credential pair and disable the default credentials", etc.
This operation is dangerous because in case of loss of those rotated credentials you might end up in a situation where you lock yourself out of a BMC.
The text was updated successfully, but these errors were encountered:
Summary
Currently we rely on the MAC DB to get the BMC secret for a given BMC device. Those are taken from the
defaultCredentials
part of the MAC DB.An example of the MAC DB looks like this:
In the current implementation of the
BMCReconciler
those initial credentials are stored in aBMCSecret
object (which is similar to a KubernetesSecret
object).In order to secure the landscape from being compromised, those initial credentials must be rotated once used for the initial BMC setup. Ideally we extend the operator to allow the admin to define the secret handling policy: e.g. "Do nothing and stick to the default credentials", "Create a new user with it's own credential pair and disable the default credentials", etc.
This operation is dangerous because in case of loss of those rotated credentials you might end up in a situation where you lock yourself out of a BMC.
The text was updated successfully, but these errors were encountered: