Changeset 1365791
- Timestamp:
- 03/07/2016 12:56:15 PM (10 years ago)
- Location:
- openam-authentication/trunk
- Files:
-
- 1 added
- 2 edited
-
README.md (modified) (7 diffs)
-
README.txt (modified) (5 diffs)
-
languages/openam-authentication.pot (added)
Legend:
- Unmodified
- Added
- Removed
-
openam-authentication/trunk/README.md
r1363992 r1365791 4 4 <b>OpenAM Authentication</b> 5 5 <table border="0"> 6 <tr><td>Contributors:</td><td>forgerock1, forgerock,marius-g,qcastel</td></tr>6 <tr><td>Contributors:</td><td>forgerock1, forgerock, marius-g, qcastel, bjornjohansen</td></tr> 7 7 <tr><td>Link:</td><td> http://www.forgerock.org/</td></tr> 8 <tr><td>Tags:</td><td> OpenAM, Authentication, REST, OpenAM 11.0.1, OpenAM 12.0, Wordpress 3.9 </td></tr>8 <tr><td>Tags:</td><td> OpenAM, Authentication, REST, OpenAM 11.0.1, OpenAM 12.0, Wordpress 3.9 & 4.4.2</td></tr> 9 9 <tr><td>Requires at least:</td><td> 3.9</td></tr> 10 <tr><td>Tested up to:</td><td>4. 1.0</td></tr>11 <tr><td>Stable tag:</td><td>1. 2.0</td></tr>10 <tr><td>Tested up to:</td><td>4.4.2</td></tr> 11 <tr><td>Stable tag:</td><td>1.4</td></tr> 12 12 <tr><td>License:</td><td> CDDLv1.0</td></tr> 13 13 <tr><td>License URL</td><td>http://forgerock.org/projects/cddlv1-0/</td></tr> … … 22 22 <br/> 23 23 The easiest way to contribute to this plugin is to submit a GitHub pull request. Here's the repo: 24 https://github.com/forgerock 1/openam-authentication24 https://github.com/forgerock/openam-authentication 25 25 <br/> 26 26 … … 41 41 <li>An OpenAM server up and running. It can be installed anywhere, as long as Wordpress can reach it. The OpenAM requires certain REST APIs, hence OpenAM 10.X and above is required. 42 42 <li> For versions of OpenAM 11.0 and older, the Legacy API mode will need to be enabled in the plugin 43 <li>Your wordpress installation up and running. This plug-in was written and tested for Wordpress 3.9.2 and 4.0.0but it might work with previous versions.43 <li>Your wordpress installation up and running. This plug-in was written and tested for Wordpress 3.9.2 up to 4.4.2 but it might work with previous versions. 44 44 </ol> 45 45 <dt> … … 55 55 How does it implement SSO with OpenAM? 56 56 <dd>It looks for a session cookie in the domain where the WordPress is installed, if there is no such session cookie, then it will require to authenticate. If the cookie is found with a session pointer valid, then the plugin will authenticate automatically to WordPress. 57 A proper cookie domain setting is necessary for SSO to work. You need to check with your OpenAM Administrator what domain is used to set the session cookie. 57 58 <dd> 58 59 Once the authentication has taken place, it will set the session in the cookie that you have configured in the plug-in (this is usually the same cookie as the one the OpenAM is using). … … 62 63 <dt> 63 64 Why did you write this plug-in? 64 <dd>We have implemented this plugin keeping in mind that the latest plugins are ob osolete and were written for OpenSSO. They have not evolved, hence have become obsolete or unusable with the newest version of Wordpress. Also this plugin takes advantage of the REST interface in OpenAM and makes it lightweight.65 <dd>We have implemented this plugin keeping in mind that the latest plugins are obsolete and were written for OpenSSO. They have not evolved, hence have become obsolete or unusable with the newest version of Wordpress. Also this plugin takes advantage of the REST interface in OpenAM and makes it lightweight. 65 66 </dl> 66 67 <br> … … 97 98 <dd>The uid and email address attribute name were hardcoded, now they are properly done. 98 99 <dd>Change a little bit the Options (Settings) page 99 </dl>100 100 <dt> 101 101 1.3 … … 104 104 <dd>Cookie Domain default option changed (Please learn about cookies and domains!) 105 105 <dd>Debugging enhancements 106 <dt> 107 1.4 108 <dd>New option to indicate what page to return in WordPress after successful OpenAM Login, when OpenAM Redirect has been enabled. 109 <dd>Cookie Domain default option fixed. The default now appears without the port component 110 </dl> -
openam-authentication/trunk/README.txt
r1363998 r1365791 1 1 === OpenAM Authentication === 2 Contributors: forgerock1, forgerock, marius-g, qcastel 2 Contributors: forgerock1, forgerock, marius-g, qcastel, bjornjohansen 3 3 Link: http://www.forgerock.org/ 4 Tags: OpenAM, Authentication, REST, OpenAM 11.0.1, OpenAM 12.0, Wordpress 3.94 Tags: OpenAM, Authentication, REST, OpenAM 11.0.1, OpenAM 12.0, OpenAM 13.0, Wordpress 3.9 & 4.4.2 5 5 Requires at least: 3.9 6 Tested up to: 4. 1.07 Stable tag: 1. 36 Tested up to: 4.4.2 7 Stable tag: 1.4 8 8 License: CDDLv1.0 9 9 License URI: https://forgerock.org/cddlv1-0/ … … 30 30 = What is it needed to make this plug-in work = 31 31 1. An OpenAM server up and running. It can be installed anywhere, as long as Wordpress can reach it. The OpenAM requires certain REST APIs, hence OpenAM 10.x and above is required. 32 2. Your wordpress installation up and running. This plug-in was written and tested for Wordpress 3.9.2 and 4.0.0, but it might work with previous versions.32 2. Your wordpress installation up and running. This plug-in was written and tested for Wordpress 3.9.2 to 4.4.2, but it might work with previous versions. 33 33 34 34 = Do I need an OpenAM Policy Agent? = … … 42 42 = How does it implement SSO with OpenAM? = 43 43 It looks for a session cookie in the domain where the WordPress is installed, if there is no such session cookie, then it will require to authenticate. If the cookie is found with a session pointer valid, then the plugin will authenticate automatically to WordPress. 44 A proper cookie domain setting is necessary for SSO to work. You need to check with your OpenAM Administrator what domain is used to set the session cookie. 44 45 45 46 Once the authentication has taken place, it will set the session in the cookie that you have configured in the plug-in (this is usually the same cookie as the one the OpenAM is using). … … 49 50 50 51 = Why did you write this plug-in? = 51 We have implemented this plugin keeping in mind that the latest plugins are ob osolete and were written for OpenSSO. They have not evolved, hence have become obsolete or unusable with the newest version of Wordpress. Also this plugin takes advantage of the REST interface in OpenAM and makes it lightweight.52 We have implemented this plugin keeping in mind that the latest plugins are obsolete and were written for OpenSSO. They have not evolved, hence have become obsolete or unusable with the newest version of Wordpress. Also this plugin takes advantage of the REST interface in OpenAM and makes it lightweight. 52 53 53 54 == Screenshots == … … 83 84 * Cookie Domain default option changed (Please learn about cookies and domains!) 84 85 * Debugging enhancements 86 = 1.4 = 87 * New option to indicate what page to return in WordPress after successful OpenAM Login, when OpenAM Redirect has been enabled. 88 * Cookie Domain default option fixed. The default now appears without the port component
Note: See TracChangeset
for help on using the changeset viewer.