Implementing FastPass
Implementing FastPass on your site is done in a few simple steps. For a general description and examples of the end-user experience of FastPass-enabled Single sign-on, please see the FastPass Overview
Conceptual Overview
The broad steps of FastPass can be summarized into the following:
- Using the chosen library a signed URL is created.
- The URL contain all the necessary information to sign the user into Get Satisfaction.
- Optionally private key/value pairs can be contained in the URL.
- There are several methods to communicate the URL to Get Satisfaction.
Choose your preferred library
By choosing the right library for you, all data below will be pre-filled for you.
Input Fields
| Field | Required | Notes |
|---|---|---|
| Key | Yes | |
| Secret | Yes | |
| Yes | ||
| Name | Yes | |
| Unique Identifier | Yes | Must remain unchanged for the lifetime of the user's account in your system. |
| Is Secure | ||
| Private Fields | Key/value pairs to send along with the user to Get Satisfaction. |
Method Signatures
Sample Call
Output:
Included files
Steps to implement FastPass
The following steps shows how to implement FastPass:
Method for passing user information
-
Using Cookies along with CNAME
Set a cookie named "fastpass" to the URL generated by the FastPass library. Note: This is only available in your company is using the CNAME feature. -
Using the Query String
Include the generated URL in the param named "fastpass" in all links to Get Satisfaction. -
Using JavaScript
When a user is logged in, include: All links to Get Satsifaction must be JavaScript function calls toGSFN.goto_gsfn()
Debugging
We have a debugger in case you have any problems. By pasting the generated FastPass URL we can provide additional information regarding whats wrong. You can find the debugger at the FastPass management page
Loading Profile...
