Storing certificates more securely when using Google APIs, OAuth 2.0 and .Net
Recently, I’ve been replacing bit.ly with the Google URL shortener service for a .Net project. It’s a pretty simple service, and the documentation shows very clearly how to get going.
Google have 3 different ways of authenticating using OAuth 2.0 (details), the method I am using is as a “Service Account”. Their code sample is thus:
The key thing that I want to draw your attention to is line 2, this implies (to me) that you are probably goign to keep the certificate in source control along with your code. This isn’t good, as it could lead quite easily to mistakenly making it public (e.g. pushing the project to GitHub).
A better solution would be to attempt to load the certificate from the local certificate store on the machine.
So that means that line 2 above, would be replaced with the following:
Things to know:
- NB: Very important, you need to make sure you call the Open method on the store, otherwise you will find that calling the Find method will never return you a certificate.
- When importing the certificate into your certificate store, make sure you include the private key, otherwise your code won’t work.