GitHub deprecating password auth

[Mark Lavagne]

Hi everyone,

Surprised it's not being discussed - GitHub is phasing out password auth. Currently GoCD seems to support password auth only in Material config dialog. Did anyone figured out how we can use key auth with GoCD?

Thank you in advance

Mark

[cal...@vertify.com]

I don't use Github but here is an article about using SSH keys with GoCD (SSH keys are supported by Github) https://stackoverflow.com/questions/43171897/how-to-set-up-gocd-to-handle-private-git-repositories-that-use-ssh-keys-for-auth

Did you try using a token in place of the password on the Material config dialog? https://docs.github.com/en/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token seems to indicate that tokens will work in place of passwords for https operations.

[Chad Wilson]

Hi Mark

If you are using HTTPS with user/pass currently you should be able to substitute a user account password in the dialog with a personal access token generated with appropriate access to your repos for GoCD to do its thing as before.

Alternatively, you can generate an SSH keypair to identify GoCD; make the keypair available in the appropriate place on the underlying server and agent operating system, and permission that public key on an account per normal. However I believe this approach requires GoCD to identify itself the same way across all repos it has access to unless you use various ssh config/clone uri hijinx to tell it which key to use for which repo. There's an example of this here, however you can also mount the keys into the approach location with appropriate permissions from a Kubernetes Secret if you are running GoCD in K8S. This approach is probably a lot clunkier if you have lots of different agent types, and not sure if there is an easier way.

-Chad

--
You received this message because you are subscribed to the Google Groups "go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email to go-cd+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/c81f3a29-d81b-41a7-a8e3-0c143adf0805n%40googlegroups.com.