943580 - Addition of ssh authorized keys equivalent on Windows machines

Status: RESOLVED DUPLICATE of bug 1035984

(Infrastructure & Operations :: RelOps: Puppet, task)

Description

[Mark Cornmesser [:markco] OOO 2024/04/15]

Puppet currently places ssh keys in a file in the .ssh directory in root's home directory. The keys also are in the following format key and user id in one line. 

KTS can not use this file. KTS will need the keys to be in the publickey_logon.ini file in the KTS directory, and needs to be in the following format:
user #
;Type ssh-dss
publickey# = key
;Comment user ID
username# =cltbld
password# =builderpassword

What needs to be figured out:
How do we source the data needed for KTS for Puppet to manage.
Build a template for puppet to manage a file with in a format which KTS can recognize the data. 
What changes will be needed to be made to the existing ssh modules to support this.

Comment 1

[Dustin J. Mitchell [:dustin] (he/him)]

This is a good question, and I don't have any good answers.  For the moment, though, let's just manage the file KTS doesn't look at, so we can get 902577 landed.

Comment 2

[Amy Rich [:arr] [:arich]]

When we rearchitect the system to do bare metal installs, we will no longer have active management of slaves.  This should be rolled into the build/capture process.