=== CryoKey ===
Contributors: cryokey
Tags: cryokey sso authentication
Requires at least: 3.4.1
Tested up to: 3.4.1
Stable tag: trunk
License: MIT
License URI: http://www.opensource.org/licenses/MIT

Allow the WordPress installation to use CryoKey authentication
if available.



== Description ==

This is the CryoKey example for WordPress. I tested it with
WordPress v3.4.1.

Under CryoKey, you log in or out using the CryoKey
certificate. Basically, if you have a valid CryoKey
certificate, you automatically view the page as the CryoKey
user. Instead of the login/logout link, you will see your
current CryoKey user name.

If you have a valid CryoKey certificate for an unknown user,
we show a _Register_ link instead of Login/Logout. If you
don't like this behavior, just comment out the relevant lines
in the `ck_check()` function.

Note that CryoKey user names are E-Mail based (but the screen
name can obviously be anything you want).

If the user doesn't have (or doesn't want to use) CryoKey
credentials, the original WordPress login flow takes place.

For more information about CryoKey, visit:
  https://www.cryokey.com

On Facebook:
  http://www.facebook.com/pages/CryoKey/473618025991948

On Twitter:
  https://twitter.com/CryoKey

On Tumblr:
  http://cryokey.tumblr.com/



== Installation ==

To use the plugin, your web server must recognize the CryoKey
CA certificate found in https://www.cryokey.com/ca.pem. For
example, in Apache's SSL configuration, you can add the lines:

    SSLCACertificateFile [path to CryoKey's CA Certificate]
    SSLVerifyClient optional
    SSLVerifyDepth 1
    <FilesMatch "\.(cgi|shtml|phtml|php)$">
      SSLOptions +StdEnvVars
    </FilesMatch>

If your WordPress directory has the `AllowOverride AuthConfig`
directive, you can instead specify the options within a
 `.htaccess` file in your WordPress directory. However, the
 `SSLCACertificateFile` (or `SSLCACertificatePath`) directives
must be in Apache's server or virtual host configuration.

Note that the configuration will not work with Safari, which
does not recognize `SSLVerifyClient optional`. If a user with
Safari connects, he will go through the normal username and
password flow.

Once you configure your web server, put __cryokey.php__ and
__ckicon.png__ into __/wp-content/plugins__. Then activate the
plugin through the _Plugins_ menu in WordPress.