When you install MettleCI Workbench (v1450 or earlier) it generates a workbench.key / workbench.key.pub key pair using an RSA encryption algorithm. This was fine up until 15th March 2022 when GitHub unexpectedly stoped accepting RSA and DSA keys. If you wish to integrate MettleCI with GitHub you should do the following… Delete (or backup, if they’re being used for anything) the existing workbench.key / workbench.key.pub key pair generate during Workbench setup. Generate a new ECDSA key pair using the command ssh-keygen -t ecdsa -b 521 -f workbench.key . Yes, that’s a 521-bit key, not 512. Ensure the sshKey: "/opt/dm/mci/workbench.key" entry in the gitAuthentication: section of your confirm.yml file is pointing to the newly-generated private key file. Register the ECDSA public key file workbench.key.pub in GitHub (see the steps herebelow). You can use the same key for accessing the DataStage and Compliance repositories so register that public key with each of those repositories. When registering the key with the Compliance repository the Engine does not require write access so feel free to leave that option deselected. Restart the Workbench service and test GitHub access by running Compliance and a Check-in from Workbench.Process
MettleCI Workbench v1451 or later generates GitHub-compliant ECDSA keys by default, so you won’t have to go through any of the above steps. | 