Project

General

Profile

Actions

coordination #105624

open

[saga][epic] Reconsider how openQA handles secrets

Added by nicksinger over 1 year ago. Updated about 1 year ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Feature requests
Target version:
Start date:
2022-01-25
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)
Difficulty:

Description

Motivation

In the ongoing effort to improve our security we introduced things like e.g. https://github.com/os-autoinst/os-autoinst/pull/1909 which is a necessary step to improve how we handle passwords/secrets.
I'd like to see that openQA also supports accessing passwords over different channels which are specifically designed to store secrets.
I know that our public cloud testers already had similar challenges. IIUC they currently use their own setup of "vault" (see 3. in Suggestions). Maybe we could unify this approach and apply it to our whole infrastructure.

Ideas

  • Support variables with arbitrary commands to access password managers like e.g. keepass (for small, local installations), pass or whatever the user decides to use.
  • Support GPG encrypted variables (and an according configuration for a private key for openQA)
  • Support common interfaces for software which is specifically designed for such use-cases. E.g. https://www.vaultproject.io/

Subtasks 3 (0 open3 closed)

openQA Infrastructure - action #106365: Improve security for OSD worker credentials broke Gitlab CI/CD deploy of salt in OSD size:MResolvednicksinger2022-01-25

Actions
openQA Infrastructure - action #106925: [timeboxed:10h][research] What are best practices and options in the salt and GitLab community to handle secretsResolvedjbaier_cz2022-02-16

Actions
action #110227: Stop showing ipmi passwords in autoinst.txt from a ipmi backend job in O3Resolved2022-04-24

Actions

Related issues 1 (0 open1 closed)

Related to openQA Project - action #104751: Extend "_SECRET_" variable handling to os-autoinst backend password variablesResolvedokurz2022-01-102022-01-24

Actions
Actions #1

Updated by nicksinger over 1 year ago

  • Copied from action #104751: Extend "_SECRET_" variable handling to os-autoinst backend password variables added
Actions #2

Updated by nicksinger over 1 year ago

  • Copied from deleted (action #104751: Extend "_SECRET_" variable handling to os-autoinst backend password variables)
Actions #3

Updated by nicksinger over 1 year ago

  • Related to action #104751: Extend "_SECRET_" variable handling to os-autoinst backend password variables added
Actions #4

Updated by okurz over 1 year ago

  • Target version set to future
Actions #5

Updated by livdywan over 1 year ago

Another instance https://openqa.opensuse.org/tests/2158135#settings which wasn't covered by #104751

Actions #7

Updated by okurz over 1 year ago

  • Tracker changed from action to coordination
  • Subject changed from Reconsider how openQA handles secrets to [saga][epic] Reconsider how openQA handles secrets
  • Priority changed from Normal to Low
Actions #8

Updated by xlai about 1 year ago

@okurz, shall #114766 be linked to this parent ticket? BTW, would you please grant me access to it?

Actions #10

Updated by livdywan about 1 year ago

xlai wrote:

@okurz, shall #114766 be linked to this parent ticket? BTW, would you please grant me access to it?

Please try again. You should have access to it.

Actions

Also available in: Atom PDF