-
Notifications
You must be signed in to change notification settings - Fork 62
Unable to use CLI with API Token #255
Comments
Hello. The API REST key is only for livedns commands. We have not implemented all other commands yet, hope it will be done soon. All other commands (except status) use API XMLRPC key. Thanks for issue and suggestion. |
Hm, I'm confused: What I am trying to tell is it's hard to understand who's who when installing the CLI for the first time. Even by reading the documentation step by step. New concepts are added at CLI setup question without being given a chance to understand. This feels enough for me:
And in case we don't have an API key yet:
|
I'm having the same issue except I cannot log in to v4 to the the API Key as my handle is not found. This is so frustrating. I've opened two different support cases so far and nothing. |
This is not resolved. Same issue on my side as well. Tested v4 and v5, and nothing is working. |
Hello, which commands are you trying to use and what is the error message ? Can you provide an output ? |
I tested both gandi cli and from python interpreter. First case was with gandi setup, with old (v4) key for xmlrpc, and new (v5) for REST. I activated production env on v4 API key settings. But always same old same output.
And from python interpreter:
EDIT: I will add command i try to use: And same command with v5, but i got it, it's not working "yet" with v5. And as somebody provided that dns part is working, i get "blank" output. 15:30 $ gandi dns list xxxxx.com |
Just a comment in case someone has the same problem I had. The command "gandi dns" works fine with just a v5 API key. So I can do e.g. gandi dns update, to change the IP of my domain, even though I do not have a v4 key. However, "gandi domain" does not work with just a v5 API key (needs v4) and that confused me at first. This seems to be a separate sub-command from gandi dns. |
Using simple curl actions with v5, is ok +-, using domains requests and not zones for dns settings, but gandi cli, and gandi dns command is not working. |
@nmarjanovic A domain can only be managed either in v4 or v5 but not in both. You must migrate a domain from v4 to LiveDNS so it can be managed in v5.
|
HI @sayoun We moved from v4 to v5. And gandi dns domain.list give blank output. I would like to share ttyrec with you, but not here. |
Can you try launching the command with debug options to see if it matches with your curl calls ? |
Sure, [DEBUG] calling url: GET https://dns.api.gandi.net/api/v5/domains |
If you have domains listed on the v5 website administration>domains>dashboards page and they are marked as using If you can go on |
Same issue with a newly generated API key for xmprpc v3. It seems this key doesn't has the format expected by the server: it has both lower and upper case characters while the server only expects lower case, as shown by this error message.
|
I was trying to use the API to create a mail forward and I had the same issues:
I was using a v5 API token from the https://account.gandi.net/fr/users/user/security admin web page. |
Same problem here :
|
Do you tech people of Gandi have some plans when LiveDNS API will support proper subset of RPC methods? With current features LiveDNS API is not serving enough use cases. |
Hello Axel.
What methods are missing for you ? Can you tell us more about your use
cases ?
Thanks.
…On Thu, Apr 25, 2019 at 2:48 PM Axel Auvinen ***@***.***> wrote:
Do you tech people of Gandi have some plans when LiveDNS API will support
proper subset of RPC methods? With current features LiveDNS API is not
serving enough use cases.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#255 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAC3WF4LWUE7GBXST53T5XTPSGSCTANCNFSM4E7MQBQQ>
.
|
Is this is the place to post priority requests for porting features from the RPC API to the new REST API? If so, I would like to promote the domains.dnssec.create function which I could use to automate rotating DNSSEC keys provided by my DNS host. |
Hi Nikolai, we're glad to take feedback to help prioritize the next features. On this specific topic what is your DNS host using? Does it support CDS/CDNSKEY rollovers? We have beta support for https://tools.ietf.org/html/draft-ietf-regext-dnsoperator-to-rrr-protocol at cdscheck.gandi.net On the more general topic of API tokens/keys and CLI usage, I think we need to address this internally, take a few decisions and publish a clear set of guidelines. |
That's great news. I use dnsimple.com as a DNS host. Do you have any pointers on how to setup CDS/CDNSKEY? |
LiveDNS + gandi CLI really does not work:
|
I think the response |
Hi, same issue. I have no idea which key to use when it comes to the XMLRPC API and it is very poorly documented :( any idea? |
@Lawouach Hi. You can ask to support team about XMLRPC API if you need to. |
Thanks will do! |
Hi, How to get an API v4 key ?! Thanks |
You can't unfortunately. That's the most bizarre way to deprecate an API before it shows up in the newer version. Gandi support is not helping at all either. |
Wtf... I'm very disappointed. I sent a request to Gandi Support (to english & french support), I hope they will help me because I need the key for a professionnal use case :( Edit : But thanks for your reply !! |
On my side, after many exchanges, they suggested they could re-enable my old Gandi access to generate one key but I told them this was not a real solution (how do I generate new ones for key management?). Support was nice but candid, finally said they'd contact R&D and never called me back... useless. |
Ok... At least that will help me for short terms use but you'r right, thats a very weird way to deprecate a website. The most weird info is their last news, they said the V4 API is not closing... Ok but they forgot the key management ?! |
The even more strange thing is that the new UI uses the REST API to make all the calls I need (TLS management). But it's not available programmatically for users, just for their dashboard... sigh. |
Ok... Thanks a lot for your feedbacks. I hope Gandi will reply me soon :) |
I take the liberty of tweeting just that without "Gandi" and without any links. |
FYI, I forgot to give a feedback. |
I ran the setup and that's what happened:
I then faced only problems and errors:
😢 welp
😢 (I just ran the setup)
I thought it would be easy but I reckon I'm running in circles.
Suggestions
What API key are you talking about?
I got confused at first when I read
Production API key for LiveDNS
on the security page. I thought it was not the right API key as cli mentionsxmlrpc
.At this stage, I no longer understand what's happening. xmlrpc? REST? LiveDNS?
I only wanted to use the CLI 😢
Easier to copy token
The text was updated successfully, but these errors were encountered: