-
Notifications
You must be signed in to change notification settings - Fork 46
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #1 from jwickard/master
Synching plugin work from svn with github.
- Loading branch information
Showing
62 changed files
with
4,775 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,115 @@ | ||
wordpress-oauth | ||
=============== | ||
# OAuth2 Complete For WordPress | ||
|
||
Plugin that enables a WordPress website to become a provider and Authenticator for Single Sign on and data transfer | ||
|
||
Contributors: Justin Greer, Joel Wickard | ||
Requires at least: 3.4.2 | ||
Tested up to: 3.7 | ||
Stable tag: 1.0.4 | ||
License: GPLv2 or later | ||
|
||
License URI: http://www.gnu.org/licenses/gpl-2.0.html | ||
|
||
Your site will be able provided Single Sign On and also deliver authorized user data using the built in OAuth 2.0 API. | ||
|
||
## Description | ||
|
||
OAuth2 Complete is a ONE OF A KIND plugin that instanly turns your WordPress webste into a valid OAuth v2 Provider. The plugin is built using OAuth2 Draft 20 standards. The backend is designed or extremly easy use for any level of experience. OAuth is a great tool but leaves most developers behind since it a bit technical. | ||
The plugin has aleady done the hard part for you. | ||
|
||
Current Features Features: | ||
|
||
* Allows for Single Sign On Abilities | ||
* Backend Panel for adding Apps/Clients | ||
* 3 Methods pre built in to allow for a plug and play system | ||
|
||
## Installation | ||
|
||
1. Upload `ouath2-complete` to the `/wp-content/plugins/` directory or use the built in plugin install by WordPress | ||
1. Activate the plugin through the 'Plugins' menu in WordPress | ||
1. Click 'Settings' and then 'permalinks'. Then simply click 'Save Changes' to flush the rewrite rules so that OAuth2 Provider | ||
1. Your Ready to Rock | ||
|
||
## Frequently Asked Questions | ||
|
||
### How do I add an APP/Client? | ||
|
||
Visit the OAuth2 Complete dashboard by clicking `Provider` in the WordPress admin panel. Once you are in teh dashboard there is a form to label `Add a Client`. Give your client a name and a redirect URI. The redirect URI is the HTTP location where the user will be returned to after authinicating (Your client should provide this for you). Click `Add Client` and you will that the client has been added to your Client Manager. | ||
|
||
### How does a client connect to my website to use the Single Sign On? | ||
|
||
Currently there is 3 Methods that OAuth2 Provider has built in: | ||
|
||
1. http://example.com/oauth/authorize | ||
|
||
1. http://example.com/oauth/request_token | ||
|
||
1. http://example.com/oauth/request_access | ||
|
||
Authorize requires only 3 parameters: | ||
|
||
* client_id | ||
* response_type - Supported value's = `code` | ||
* state | ||
* Example call `http://example.com/oauth/authorize?client_id=the_client_id&state=anything_you_want&response_type=code` | ||
|
||
Request Token Requires only 4 parameters | ||
|
||
* code - This is auth code returned from the authorize call | ||
* grant_type - Supported value's = `authorization_code` | ||
* client_id | ||
* client_secret | ||
* Example call `http://example.com/oauth/request_token?code=the_auth_key_sent_back_from_the_authorize_call&grant_typ=authorization_code&client_id=the_client_id&client_secret=the_client_secret` | ||
|
||
Request Access Requires only 1 parmeter | ||
|
||
* access_token - This is the access_token provided from the Request Token call | ||
* Example Call `http://example.com/oauth/request_access?access_token=the_token_from_the_request_call` | ||
|
||
|
||
NOTE: All returns will be in JSON format. | ||
|
||
### Is there support for this plugin? Can you help me? | ||
|
||
You can visit our <a href="http://justin-greer.com/forums/forum/wordpress-oauth2-provider-plugin/" title="WordPress OAuth2 Provider Plugin">support forum</a> for support. Although it takes the hard part away from dealing with OAuth it will require some knowledge on your behalf. I am glad to help as much as resonibily possible but there has to be a line drawn somewhere. | ||
|
||
### Can you set this up for me on my current website? | ||
|
||
Can I? "YES". But thats a different story. You are more than welcome to contact us with if you should ever need assistance. | ||
|
||
### What information does the a authorized client have access to? | ||
|
||
By default OAuth2 Provider delivers <strong>ALL</strong> the information about the user that logged in. We are planning on adding a easy to use dashboard to limit data. | ||
|
||
### Do you have a tutorial I can follow ? | ||
|
||
Yes I do. You can view a video titorial here. If you prefer readin then you may have to wait until the full documentation is complete. I are working hard to make it as easy and painless as possible for you to have a premium feature. | ||
|
||
### Where can I download the SDK's for OAuth2 Provider | ||
|
||
You can visit my websiet <a href="http://justin-greer.com">Here</a> | ||
|
||
## Upgrade Notice | ||
|
||
When Upgrading OAuth2 Provider I serioulsy recommend creating a backup of your site. I will try to create updates that will be flawless. Hopefully any future updates will not chnage to the point where it will stop working. All updates will be ran through multiple tests before being released. In the event that the a upgrade of OAuth2 Provider is realeased and you decide to update, I (Justin Greer) can not and will not be held responsible for any damages done to your website, business, or part that pertains to your website. Upgrade at your OWN RISK! | ||
|
||
## Screenshots | ||
|
||
## Changelog | ||
|
||
### 1.0.0 | ||
*INITIAL BUILD | ||
|
||
### 1.0.1 | ||
* Re-worked Readme.txt | ||
* Fixed absolute paths causing 404 Error when WordPress is running under a sub directory (Using admin_url() currently) | ||
|
||
### 1.0.2 | ||
* Fixed Broken login redirect | ||
|
||
### 1.0.3 | ||
* Fixed Admin URL links for plugin dashboard | ||
|
||
### 1.0.4 | ||
* Fixed short tag in login layout | ||
* Filtered out hashed password / user activation key from returned oauth data. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,43 @@ | ||
.quick_search { | ||
text-align: center; | ||
padding: 14px 0 0px 0; | ||
} | ||
|
||
.quick_search input[type=text] { | ||
text-align: left; | ||
height: 22px; | ||
width: 88%; | ||
color: #ccc; | ||
padding-left: 2%; | ||
padding-top: 5px; | ||
background: #fff url(../images/icn_search.png) no-repeat; | ||
background-position: 10px 6px; | ||
} | ||
|
||
.toggleLink { | ||
display: inline; | ||
float: none; | ||
margin-left: 2% | ||
} | ||
|
||
html ul.tabs li.active, html ul.tabs li.active a:hover { | ||
background: #ccc; | ||
} | ||
|
||
input[type=submit].btn_post_message { | ||
background: url(../images/post_message.png) no-repeat; | ||
} | ||
|
||
fieldset input[type=text] { | ||
margin-left: -10px; | ||
} | ||
|
||
|
||
fieldset select { | ||
margin-left: -10px | ||
} | ||
|
||
fieldset textarea { | ||
margin-left: -10px; | ||
} | ||
|
Oops, something went wrong.