The Rails Integration_API plugin enables single sign-on between a
Rails application and any number of WordPress installations.
| Author: | robbpdx (profile at wordpress.org) |
| WordPress version required: | 2.6.3 |
| WordPress version tested: | 2.6.3 |
| Plugin version: | 0.0 |
| Added to WordPress repository: | 03-11-2008 |
| Last updated: | 03-11-2008
Warning! This plugin has not been updated in over 2 years. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.
|
| Rating, %: | 0 |
| Rated by: | 0 |
| Plugin URI: | http://greenfabric.com/page/integration_api_h... |
| Total downloads: | 1 677 |
| Active installs: | 10+ |
 Click to start download |
|
This plugin enables single sign-on between a Rails application and any number of WordPress installations. You can view an online demo showing a Rails app integrated with a WordPress app.
The key idea of the Integration API is to add a web services API into the existing Rails application, which allows one or more 3rd party apps to get the information they need, when they need it.
The API code can be added to any Rails app without modification. The Rails app stays in control of all sign-in and sign-out functions.
The 3rd party app, such as WordPress, is installed in a subdirectory of the Rails app on the same host. Alternatively, it can be installed running on a different port. These configurations will allow it to access the Rails cookie, which it needs to do to verify that the current user is logged in.
This plugin gives the administrator a couple of options about how the tight the integration should be (see the screenshots):
- Single sign-on This can be switched on or off. When on, Wordpress will check the user's Rails login state on every page view, and update the WordPress cookie and login state automatically. When off, the user will need to explicitly click the WordPress login and logout links.
- Automatically create new users This can also be switched on and off. It determines what happens when a user, logged in to Rails, first accesses WordPress. It allows the administrator to maintain manual control of who has login access, vs. allowing all Rails users to have login access to WordPress.