Gandi Dynamic DNS update using PAT instead of API-Key
-
Hello,
I used Gandi to update my DNS entries using the API-Key Gandi provided. However, they moved away from offering API Keys and are now offering Personal Access Tokens (PAT). The authentication is just a little bit different now. Maybe someone at Netgate could copy the current Service Type and change it according to Gandis documentation.
I'd be willing to test it on my 4200, if someone could change it.
Cheers
Max -
Here is a link of a topic where @evantill added Gandi LiveDNS Support using API-Key to pfSense:
2018: Dynamic DNS support for Gandi LiveDNS?From "Authorization: Apikey 0123456" to "Authorization: CustomName 0123456" might be everything that needs to be done.
As far as I know it'd be possible to dublicate the commit and add the PAT Support easily for someone who is a little bit more involved with git/redmine.
-
ITSGS that post doesn't help it's from 2018.
The built in dynamic dns client works fine with an API key, but these are not deprecated, and Gandi are using Personal Access Tokens (PATs), when trying to input the PAT into the built in integration it fails with a 403.
I have been able to re-issue the older API key via Gandi instead of a PAT and it's all working again, I suspect the built in integration needs to updated to support PATs.
-
@saqibs Yes, it needs two parameters instead of one. Hopefully someone can help us out.
-
Update: Check release notes of 25.03. PAT will be added with the 25.03 release. Using the Beta I was able to confirm that updating DNS entries using PAT works.
-
@ITSGS_
thanks for this, just checked the notes for CE 2.8.0 here:and it looks like they have moved from API to PAT in this release:
Users of the Gandi Dynamic DNS service must change their current API token to a Personal Access Token (PAT) as Gandi now requires this authentication method for Dynamic DNS updates. For uninterrupted Dynamic DNS service, create a new PAT and save that PAT value in Gandi Dynamic DNS entries before upgrading to this release.