Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author David Anderson

    (@davidanderson)

    Hi,

    We inherited this feature from the plugin we forked. Looking at the current code, it doesn’t seem like it can work. It looks for a POST-ed parameter, tfa, containing a valid TFA code, but that isn’t compatible with XML-RPC. I suppose it should look in GET instead when XML-RPC is in use. This would mean that your app should either ask for a code each time it sends data, or ask for the private key and generate a code as-and-when needed, and send it as a URL parameter. Does this seem sensible?

    However, having said all of that, XML-RPC is considered legacy; you ought to be looking at the new REST API. This uses OAuth, a standard protocol, and is a much better idea. Relevant links:

    https://make.www.ads-software.com/core/2015/09/21/wp-rest-api-merge-proposal/
    https://www.ads-software.com/plugins/json-rest-api/
    https://v2.wp-api.org/

    Thread Starter opensourceninja

    (@opensourceninja)

    Sorry for taking so long to respond ??
    I think it would make sense in my case for my app to ask for the private key and generate a one-time code using TOTP.

    I’ll definitely look into supporting the REST API too.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘How to use XML-RPC with this?’ is closed to new replies.