Eric Mann

<p>Rather than sending usernames and passwords in plain text with every request, we’re going to use a set of public/secret keys to hash data and authenticate instead.</p>
<p>On your WordPress profile, you will see a new “Remote Publishing Permissions” section listing out the applications that have permission to publish, along with their public and secret keys.</p>
<p>New applications can be added whenever you want.  You can also change the names of applications, or revoke publishing permission by deleting them.</p>
<h3>Additional Information</h3>
<p>Lock graphic designed by Scott Lewis from the thenounproject.com</p>


Secure XML-RPC

More secure wrapper for the WordPress XML-RPC interface.

DeveloperWil

<p>Completely disables the XML-RPC API which was introduced in WordPress 3.5 and above which lets remote clients post, upload and edit content.</p>
<p>Notes:<br />
If you are using the WordPress smart phone app or the Jetpack plugin, please note that they need this service enabled.</p>
<p>If you activate this plugin your WordPress phone app will not be able to connect to your site and Jetpack will not be able to connect to wordpress.com where site visitor data (and other stuff) is stored.</p>
<p>Other plugins and services that use the XML-RPC API will also not function properly.</p>
<h4>Plugin Page</h4>
<p><a href="https://zeropointdevelopment.com/wordpress-plugins/deactivate-xml-rpc-service-wordpress-plugin/" title="Deactivate XML-RPC Service WordPress Plugin" rel="nofollow ugc">Deactivate XML-RPC</a></p>


Deactivate XML-RPC Service

Disables the XMP-RPC API service introduced in WordPress 3.5 and above.

Secure XML-RPC vs Deactivate XML-RPC Service