GDv2 REST API Authentication Not Working – Invalid Signature

This topic contains 2 replies, has 2 voices, and was last updated by  Philippe Bertrand 4 years, 9 months ago.

We have moved to a support ticketing system and our forums are now closed.

Open Support Ticket

Tagged: , ,

  • Author
    Posts
  • #527048

    Philippe Bertrand
    Expired Member
    Post count: 1

    We’re trying to use the REST API to automatically create a listing (e.g. gd_places) from the WordPress PHP backend. Since it’s on HTTP local dev machine, we’re using OAuth 1.0a for authentication. After delving into GeoDirectory’s plugin for REST authentication, all the proper OAuth params (e.g. oauth_signature, oauth_consumer_key, etc.) have been implemented.

    However, whenever the request is made, we get the error “Invalid signature – provided signature does not match”.

    Trying with Basic Authentication on an HTTPS server with REST API enabled with all proper keys, it fails w/o error message, but the listing is NOT created. Instead, the response is the list of all current listings in that category as though a GET request was made.

    We did not see any documentation on GeoDirectory’s site as to how to properly configure OAuth or any other authentication means to access the API from the backend.

    #527071

    Alex Rollin
    Moderator
    Post count: 27815

    Hello,

    authentication is not included, that is true. There are a wide variety of plugins and methods for securing the endpoint and we have not included one with GeoDirectory.

    #527094

    Philippe Bertrand
    Expired Member
    Post count: 1

    Ok, thank you. For now, we’re going with an alternative approach to create the listing dynamically from the interface instead of the backend.

Viewing 3 posts - 1 through 3 (of 3 total)

We have moved to a support ticketing system and our forums are now closed.

Open Support Ticket
20% Discount Offer
Hurry! Get your 20% discount before it expires. Get 20% Discount