Reply
Highlighted
Accepted Solution

WAPI calls failing to work after product upgrade from 8.2.4 to 8.4.1

goatman
Techie
Posts: 3
364     0

Hello, experts!

 

I have been using curl to access Infoblox via WAPI, to search for aliases and cnames.

 

The following command was working last week, but after the weekend upgrade to the base product, it has stopped giving results:

 

curl -s -k -u usernm:p4ssw0rd -X -H "Content-Type:application/json" -d _return_fields=aliases -d name:=mysrvr.tld.com -X GET https://prog.tld.com/wapi/v2.7/record:host

 

Before the upgrade, it would return "[]" for empty sets, or auth errors when necessary...Something!  Now, however, it is an empty return.

 

I was able to get this to work:

 curl -s -k -u usernm:p4ssw0rd -X -H "Content-Type:application/json" -X GET  https://prog.tld.com/wapi/v2.7/record:host

 

Did the searches get pickier in the later version?

Re: WAPI calls failing to work after product upgrade from 8.2.4 to 8.4.1

goatman
Techie
Posts: 3
365     0

<bump>

 

Anyone have any ideas? 

 

Even if someone would post a working curl for WAPI v2.9.1, that uses GET, and one or two parameters...

 

Thanks!

Re: WAPI calls failing to work after product upgrade from 8.2.4 to 8.4.1

Ingmar Community Manager
Community Manager
Posts: 42
365     0

I tried to replicate it on 8.4.2 and got the [] response when there was no data. There might be an issue with 8.4.1 but it looks like it works now. I  used the v2.10 as well as v2.7 api and it looks like the results are consistent between them.

 

At this point I believe a support case and some more detailed data gathering will be required

 

curl  -s -k -u admin:infoblox -X GET https://10.1.1.1/wapi/v2.10/record:host
[]

Re: WAPI calls failing to work after product upgrade from 8.2.4 to 8.4.1

goatman
Techie
Posts: 3
365     0

Egads, I hate to be "that guy", but now it is working!

 

Thanks so much for your reply, Ingmar...

Showing results for 
Search instead for 
Do you mean 

Recommended for You