Configuring the ScreenSteps Remote Authentication WordPress Plugin

This lesson will show you how to configure the ScreenSteps Live Remote Login WordPress plugin.

Load Plugin Settings Page

Click on ScreenSteps Live Remote Login plugin settings link.

Load Plugin Settings Page

On the plugin settings page you will need to enter two pieces of information.

  1. The Remote Authentication Consumer URL
  2. Your remote authorization token

Begin by entering your ScreenSteps domain. Next I will show you how to get your remote authorization token.

Enable Remote Authentication

If you haven't already, create a Remote Authentication Endpoint on your ScreenSteps account. You will create a ScreenSteps Remote Auth endpoint (not SAML).

Enter Remote Login URL

  1. Give the endpoint an descriptive name like WordPress.
  2. Now you need to tell ScreenSteps where it should send people when they need to log in to see protected ScreenSteps content. For the Remote Login URL you need to enter the path to the WordPress login page along with a special variable called ss_live_remote_login. Your url should look something like this:
http://www.mydomain.com/myblog/wp-login.php?sslive_remote_login=1
Enter Remote Login URL

Add Remote Authentication Token and Remote Consumer URL to WordPress Plugin

Copy the Remote Authentication Token and the Remote Consumer URL values into the WordPress plugin fields.

Click Save Settings in WordPress.

Add Remote Authentication Token and Remote Consumer URL to WordPress Plugin

Try to access protected content in ScreenSteps

Now try to access a protected resource in ScreenSteps.

Try to access protected content in ScreenSteps

You will be redirected to the WordPress login page. After successfully logging in using the WordPress form you will be redirected to the ScreenSteps resource you requested.

Note: If you need to log into ScreenSteps using the standard login form you can always access it at:

http://YOUR_SUBDOMAIN.screenstepslive.com/login/normal

0 Comments

Add your comment

E-Mail me when someone replies to this comment