Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add credential rotation of BMCSecrets #67

Open
afritzler opened this issue Jul 2, 2024 · 0 comments
Open

Add credential rotation of BMCSecrets #67

afritzler opened this issue Jul 2, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@afritzler
Copy link
Member

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:

macPrefixes:
- macPrefix: 23
  manufacturer: Foo
  protocol: Redfish
  port: 8000
  type: bmc
  defaultCredentials:
  - username: foo
    password: bar

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.

@afritzler afritzler added the enhancement New feature or request label Jul 2, 2024
@afritzler afritzler changed the title Add credential rotation to BMCSecrets Add credential rotation of BMCSecrets Jul 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Ready
Development

No branches or pull requests

1 participant