[GH-ISSUE #372] Feature Request - accept and record a "note" (max 64 chars) with `/register` endpoint #209

New issue

Open

opened 2026-03-13 16:09:42 +03:00 by kerem · 0 comments

kerem commented

2026-03-13 16:09:42 +03:00

Owner

Originally created by @jvanasco on GitHub (Jan 8, 2025).
Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/372

It would be useful if a user could pass a generic message (max 64 ascii chars) to the /register endpoint, which is then saved to the records table alongside the newly generated account.

The use-case: I would like to pass in an identifier (FQDN, application id, test-information, etc) when generating an acme-dns account on /register, to help identify records solely within the acme-dns database. This would greatly simplify audits of the acme-dns database to identify stale data that can be safely removed (an old LastUpdate might be for a domain that is still enrolled in the system, but currently using http-01). This would also make it easier to handle testing against a staging server, and make some local testing easier as well.

Originally created by @jvanasco on GitHub (Jan 8, 2025). Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/372 It would be useful if a user could pass a generic message (max 64 ascii chars) to the `/register` endpoint, which is then saved to the `records` table alongside the newly generated account. The use-case: I would like to pass in an identifier (FQDN, application id, test-information, etc) when generating an acme-dns account on `/register`, to help identify records solely within the acme-dns database. This would greatly simplify audits of the acme-dns database to identify stale data that can be safely removed (an old `LastUpdate` might be for a domain that is still enrolled in the system, but currently using `http-01`). This would also make it easier to handle testing against a staging server, and make some local testing easier as well.