Plugin Directory

Changeset 1365791


Ignore:
Timestamp:
03/07/2016 12:56:15 PM (10 years ago)
Author:
victor.ake
Message:

Updating the POT file

Location:
openam-authentication/trunk
Files:
1 added
2 edited

Legend:

Unmodified
Added
Removed
  • openam-authentication/trunk/README.md

    r1363992 r1365791  
    44<b>OpenAM Authentication</b>
    55<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>
    77<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>
    99<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>
    1212<tr><td>License:</td><td> CDDLv1.0</td></tr>
    1313<tr><td>License URL</td><td>http://forgerock.org/projects/cddlv1-0/</td></tr>
     
    2222<br/>
    2323The easiest way to contribute to this plugin is to submit a GitHub pull request. Here's the repo:
    24 https://github.com/forgerock1/openam-authentication
     24https://github.com/forgerock/openam-authentication
    2525<br/>
    2626
     
    4141<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.
    4242<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.0 but 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.
    4444</ol>
    4545<dt>
     
    5555How does it implement SSO with OpenAM?
    5656<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.
     57A 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.
    5758<dd>
    5859Once 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).
     
    6263<dt>
    6364Why did you write this plug-in?
    64 <dd>We have implemented this plugin keeping in mind that the latest plugins are obosolete 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. 
    6566</dl>
    6667<br>
     
    9798<dd>The uid and email address attribute name were hardcoded, now they are properly done.
    9899<dd>Change a little bit the Options (Settings) page
    99 </dl>
    100100<dt>
    1011011.3
     
    104104<dd>Cookie Domain default option changed (Please learn about cookies and domains!)
    105105<dd>Debugging enhancements
     106<dt>
     1071.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  
    11=== OpenAM Authentication ===
    2 Contributors: forgerock1, forgerock, marius-g, qcastel
     2Contributors: forgerock1, forgerock, marius-g, qcastel, bjornjohansen
    33Link: http://www.forgerock.org/
    4 Tags: OpenAM, Authentication, REST, OpenAM 11.0.1, OpenAM 12.0, Wordpress 3.9
     4Tags: OpenAM, Authentication, REST, OpenAM 11.0.1, OpenAM 12.0, OpenAM 13.0, Wordpress 3.9 & 4.4.2
    55Requires at least: 3.9
    6 Tested up to: 4.1.0
    7 Stable tag: 1.3
     6Tested up to: 4.4.2
     7Stable tag: 1.4
    88License: CDDLv1.0
    99License URI: https://forgerock.org/cddlv1-0/
     
    3030= What is it needed to make this plug-in work =
    31311. 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.
     322. 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.
    3333
    3434= Do I need an OpenAM Policy Agent? =
     
    4242= How does it implement SSO with OpenAM? =
    4343It 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.
     44A 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.
    4445
    4546Once 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).
     
    4950
    5051= Why did you write this plug-in? =
    51 We have implemented this plugin keeping in mind that the latest plugins are obosolete 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. 
     52We 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. 
    5253
    5354== Screenshots ==
     
    8384* Cookie Domain default option changed (Please learn about cookies and domains!)
    8485* 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.