Google Cloud DNS for Let's Encrypt / ACME dns-01 challenges with ACME.js and Greenlock.js
Go to file
AJ ONeal e612d57912 update docs and examples for auth 2019-07-23 20:39:46 -06:00
lib update docs and examples for auth 2019-07-23 20:39:46 -06:00
.gitignore add template, implement auth and zones 2019-07-23 00:53:39 -06:00
AUTHORS add template, implement auth and zones 2019-07-23 00:53:39 -06:00
LICENSE Initial commit 2019-07-23 05:21:59 +00:00
README.md update docs and examples for auth 2019-07-23 20:39:46 -06:00
example.env update docs and examples for auth 2019-07-23 20:39:46 -06:00
index.js add template, implement auth and zones 2019-07-23 00:53:39 -06:00
oauth2l-test-token.sh update docs and examples for auth 2019-07-23 20:39:46 -06:00
package-lock.json update docs and examples for auth 2019-07-23 20:39:46 -06:00
package.json add package.json 2019-07-23 01:34:48 -06:00
test.js update docs and examples for auth 2019-07-23 20:39:46 -06:00

README.md

acme-dns-01-googlecloud.js

Google Domains + Let's Encrypt for Node.js - ACME dns-01 challenges w/ ACME.js and Greenlock.js

In Progress. Would love help. Please contact @coolaj86 on Keybase.

  • zones
  • set
  • get
  • remove

Implementation Details

Authenticating

Google has made things way too complicated.

Test This First!

Edit the file oauth2l-test-token.sh

Change the location of service_account.json to whatever it needs to be.

Change the PROJECT to the name of your project.

If that doesn't work, something is wrong with your credentials, nothing else will work.

Usage

First you create an instance with your credentials:

var dns01 = require('acme-dns-01-googlecloud').create({
	baseUrl: 'https://www.googleapis.com/dns/v1/', // default

	// contains private_key, private_key_id, project_id, and client_email
	serviceAccountPath: __dirname + '/service_account.json'
});