Role Of Oauth 2 In WordPress

WordPress is a powerful personal publishing platform that has strong focus on aesthetics, web standards and great usability. WordPress is used by developers for wordpress development which adds to the looks of the blog and websites. WordPress company has added the support for authentication protocol OAuth 2 to because they want wordpress to be much more than a simple web based blogging software service. WordPress developers can now easily connect third party apps with wordpress blogs through this secure OAuth 2. In this article we will discuss about it and see how wordpress developers can easily configure their applications to get the ability to access the blog even without asking for personal details like username or password. OAuth2 is a protocol which allows apps and partners to interact with the blogs on WordPress development has gained immense popularity with the amazing features introduced continuously. Basic aim behind offering OAuth2 support is to allow interaction between wordpress developers and without any necessity of storing sensitive credentials. Users are free to manage their own connections with its implementation. Doesn’t matter if you are a fresher you can find more details or information at And if you are familiar with OAuth2 then you require very little knowledge to know about two end points that is the authorization endpoint and token endpoint. WordPress developers need to create a client id and a client secret key before they start with the development of an application. These both are needed for authentication of your application and for verification of the calls whether they are been made to are valid or not. As seeing the current situation they are granting only a limited access. Receiving an Access Token: If you want to act on the behalf of users and make calls from API then you will need an access token. To get it you are required to go through the access token flow and then prompt the user to authorize the application. These tokens are given per blog per user so it means that you require a different access token for each blog that a user owns and you want to access. For beginning send the user to authorization end point. In the next step a code will be included to redirect the application and in case the user denies access then redirect will include: ?error=access_denied The other option is that you may also pass along a blog parameter with the URL to the blog. At the time you are done with the authorization of the request your clients will be redirected to the redirect_url which will look like: With the use of time-limited code, your application is able to exchange full authorization token. To fulfil this task make a POST request like: 01    $curl = curl_init( "" ); 02    curl_setopt( $curl, CURLOPT_POST, true ); 03    curl_setopt( $curl, CURLOPT_POSTFIELDS, array( 04    ‘client_id’ =>your_client_id, 05    ‘redirect_uri’ =>your_url, 06    ‘client_secret’ =>your_client_secret_key, 07    ‘code’ => $_GET[‘code’], 08    ‘grant_type’ => ‘authorization_code’ 09    ) ); 10    curl_setopt( $curl, CURLOPT_RETURNTRANSFER, 1); 11    $auth = curl_exec( $curl ); 12    $secret = json_decode($auth); 13    $access_key = $secret->access_token; Then passclient_id, client_secret, and redirect_uri which should match with your application’s parameters. You will receive a JSON-encoded string that contains token and some basic information about the blog: {"access_token":"——–","token_type":"bearer","blog_id":"blog id","blog_url":"blog url"} After getting the access token it should be stored securely with the blog id and blog url. Your application is ready to act on behalf of the user on this specific blog. – – – – – – – – – – 相关的主题文章: