Feature #9639
closedCloudflare DDNS "API Token"
100%
Description
Request to add support for new Cloudflare API Token to allow for managed access and permissions for DDNS updates.
API Tokens use the standard Authorization: Bearer header for authentication instead of x-auth-email and x-auth-key that API Keys use. Requests can be authenticated like the following:
curl -X GET "https://api.cloudflare.com/client/v4/zones/cd7d0123e3012345da9420df9514dad0" \
-H "Content-Type:application/json" \
-H "Authorization: Bearer 1234567893feefc5f0q5000bfo0c38d90bbeb"
Updated by theodore adams about 5 years ago
theodore adams wrote:
Request to add support for new Cloudflare API Token to allow for managed access and permissions for DDNS updates.
API Tokens use the standard Authorization: Bearer header for authentication instead of x-auth-email and x-auth-key that API Keys use. Requests can be authenticated like the following:
curl -X GET "https://api.cloudflare.com/client/v4/zones/cd7d0123e3012345da9420df9514dad0" \
-H "Content-Type:application/json" \
-H "Authorization: Bearer 1234567893feefc5f0q5000bfo0c38d90bbeb"
This feature has now been released generally:
https://blog.cloudflare.com/api-tokens-general-availability/
Updated by John M almost 5 years ago
+1 to getting them supported in the Dynamic DNS service.
They are already supported in the "acme" plugin, but they need to be supported in Dynamic DNS as well.
Updated by DRago_Angel [InV@DER] almost 5 years ago
+1 as well to get it, I created workaround to get it work, but native will be better in many ways https://forum.netgate.com/topic/149294/ddns-cloudflare
Updated by Renato Botelho almost 5 years ago
- Status changed from New to Feedback
- Assignee set to Renato Botelho
- Target version set to 2.5.0
- % Done changed from 0 to 100
PR has been merged. Thanks!
Updated by Renato Botelho about 4 years ago
Updated by Danilo Zrenjanin about 4 years ago
- Status changed from Feedback to Resolved
Tested on :
2.5.0-DEVELOPMENT (amd64) built on Thu Sep 17 13:55:47 EDT 2020 FreeBSD 12.2-PRERELEASE
against the generated API token which allows managed access and permissions.
Works fine.
Ticket resolved.