How Do I Remotely Authenticate a User using ScreenSteps Live Remote Authentication?

When ScreenSteps Live redirects a user to your remote authentication url it sends along a couple of pieces of information in the query parameters:

• return_to_url: This is the url that the user requested on ScreenSteps Live. You will pass this back to ScreenSteps Live after the user authenticates so that ScreenSteps Live can display the requested resource to the user.

• timestamp: This is the time value that you can use when generating the MD5 hash.

In order to information ScreenSteps Live that a user has permission to view content you must pass over an MD5 hash. The MD5 has is comprised of:

1) First name of the user
2) Last name of the user
3) Email of the user
4) External id (used to uniquely identify user, can be empty in which case email is used)
5) Organization (can be empty)
6) ScreenSteps Live remote authentication token (look in ScreenSteps Live Settings)
7) Time (unix time)

To notify ScreenSteps Live that a user has successfully logged in you redirect to a url and pass a number of parameters. The url you redirect is your ScreenSteps Live domain followed by /login/remote/. For example:

http://example.screenstepslive.com/login/remote

You can pass the rest of the information needed as GET parameters in the query string. You must pass all of the information used to make the MD5 hash EXCEPT for your ScreenSteps Live remote authentication token (this must remain secret). An example (broken up into multiple lines for readability):

http://example.screenstepslive.com/login/remote/?
first_name=FIRST_NAME&last_name=LAST_NAME&email=you%40domain.com&
external_id=EXTERNAL_ID&organization=ORGANIZATION&timestamp=TIMESTAMP&
hash=MD5_HASH&return_to_url=RETURN_TO_URL

By passing over the information used to create the hash ScreenSteps Live can combine the secret remote authentication token with the information you passed over in order to confirm that the hash is valid. This keeps others from being able to log users in.