Skip to content

Read AMT, MPS, and CIRA APF credentials from Vault for RPS-provisioned devices #676

Closed

Description

@amarnath-ac

Description:
RPS does not send AMT or MPS passwords over the device API. It writes them to the shared Vault under devices/{guid} at activation. Console must use the same secret object when the device row has no stored password. For CIRA, this includes APF authentication against MPS_PASSWORD; for WSMAN, use AMT_PASSWORD with username admin.

Expected:
Console uses a non-empty stored device password first, then falls back to the matching Vault value. Missing Vault configuration or a failed read is logged and does not fail the request; deployments without Vault retain existing behavior.

Acceptance criteria:

  • WSMAN succeeds for an RPS-provisioned device using AMT_PASSWORD from Vault and username admin.
  • The CIRA APF tunnel authenticates using MPS_PASSWORD from Vault when the device row has none.
  • A Vault read failure is logged and follows the existing no-credential/failure behavior without crashing or blocking unrelated requests.
  • Stored device passwords take precedence over Vault fallback values.
  • Deployments without Vault and devices with database-stored credentials continue to work.
  • Vault-only values are not persisted back into the device row or returned in API responses.

Activity

  1. self-assigned this
    on Sep 23, 2026
  2. moved this to In Progress in Sprint Planningon Sep 23, 2026
  3. added theissue type on Sep 23, 2026
  4. changed the title [-]Read AMT and MPS passwords from Vault for devices provisioned by RPS[/-] [+]Read AMT, MPS, and CIRA APF credentials from Vault for RPS-provisioned devices[/+] on Oct 13, 2026
  5. amarnath-ac commented on Oct 28, 2026

    @amarnath-ac
    ContributorAuthor

    Based on the decision that Vault won't be used for credentials: Console will get AMT/MPS/CIRA APF passwords directly from RPS, and store them in its own database, instead of Console reading them from Vault. Closing this in favor of that approach.

  6. moved this from In Progress to Done in Sprint Planningon Oct 28, 2026
  7. amarnath-ac commented on Oct 28, 2026

    @amarnath-ac
    ContributorAuthor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

v3-readinessTracks remaining work required before the v3 release

Type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions