News for hackers. Stuff that matters.

A comment on Nginx Introduces Native Support for Acme Protocol. Parent comment

Re:Nginx Introduces Native Support for Acme Protocol by teruakohatu on Thursday August 14, 2025 @01:49AM (#44897132)
This has blown my mind. Its been a constant source of frustration since Cloudflare stubbornly refuses to allow non-enterprise accounts to have a seperate key per zone. The thread requesting it is a masterclass in passive aggressiveness:

https://community.cloudflare.com/t/restrict-scope-api-tokens...

[ Parent | on HN ]
Re:Nginx Introduces Native Support for Acme Protocol by Jnr on Thursday August 14, 2025 @02:18AM (#44897268)
When setting up the API key, use the "Select zones to include or exclude." section. Works fine on the free account.
[ Parent | on HN ]
Re:Nginx Introduces Native Support for Acme Protocol by teruakohatu on Thursday August 14, 2025 @05:25AM (#44898456)
I should have clarified, you can’t for subdomains on a non-enterprise account.
[ Parent | on HN ]
Re:Nginx Introduces Native Support for Acme Protocol by Kovah on Thursday August 14, 2025 @02:11AM (#44897239)
Could you elaborate on the separate key per zone issue? It's possible to create different API keys which have only access to a specific zone, and I'm a non-enterprise user.
[ Parent | on HN ]
Re:Nginx Introduces Native Support for Acme Protocol by johnmaguire on Thursday August 14, 2025 @02:24AM (#44897310)
This allows you to restrict it to a domain (e.g. example.com) but not a sub-domain of that domain.
[ Parent | on HN ]
Re:Nginx Introduces Native Support for Acme Protocol by Kovah on Thursday August 14, 2025 @03:05AM (#44897555)
Ah I see, thanks for the clarification!
[ Parent | on HN ]