Loading Profile...
Confusions Implementing Fastpass
Dear Get Sat,
I'm afraid it's either me or the docs. EIther way, I'm confused about exactly how to implement Fastpass. I'm not sure if it's my understanding of the general concept, or if it's specific implementation details.
Currently I've tried used direct URL link. I generate a URL from FastPass util and paste this URL into my browser - all I get is a javascript file. Not sure what I am supposed to do with this.
If I paste the same URL into the debugger on the admin page, it comes up as all green.
I've also tried tried the script generation. My first confusion is that I'm not sure what HTML page this is supposed to go on, on what to expect it to do. Following it, it appears to place some javascript tags into to the page header.
But then the page does nothing.
My concept is that I just generate a URL and forward the user's browser to it, and he'll be logged into Get Sat as if by magic. Is that not correct? Why does it need javascript?
Also, I'm not at all sure how this fits into the explanations of OAuth model I've seen elsewhere.
Are there any docs which are:
1 - detailed
2 - assume nothing in terms of prior Get Sat or OAuth knowledge
3 - explain exactly what is supposed to happen and what needs to be done, at a technical level
Currently there is a workflow overview, which looks just great, but then the technical pages are just a collection of code snippets and a kind of "just plug it in and it'll work" description, which is of no use when it doesn't work.
Is there a checklist of things I might be doing wrong? (Not a checklist of things that might be wrong with the URL.)
Stewart
I'm afraid it's either me or the docs. EIther way, I'm confused about exactly how to implement Fastpass. I'm not sure if it's my understanding of the general concept, or if it's specific implementation details.
Currently I've tried used direct URL link. I generate a URL from FastPass util and paste this URL into my browser - all I get is a javascript file. Not sure what I am supposed to do with this.
If I paste the same URL into the debugger on the admin page, it comes up as all green.
I've also tried tried the script generation. My first confusion is that I'm not sure what HTML page this is supposed to go on, on what to expect it to do. Following it, it appears to place some javascript tags into to the page header.
But then the page does nothing.
My concept is that I just generate a URL and forward the user's browser to it, and he'll be logged into Get Sat as if by magic. Is that not correct? Why does it need javascript?
Also, I'm not at all sure how this fits into the explanations of OAuth model I've seen elsewhere.
Are there any docs which are:
1 - detailed
2 - assume nothing in terms of prior Get Sat or OAuth knowledge
3 - explain exactly what is supposed to happen and what needs to be done, at a technical level
Currently there is a workflow overview, which looks just great, but then the technical pages are just a collection of code snippets and a kind of "just plug it in and it'll work" description, which is of no use when it doesn't work.
Is there a checklist of things I might be doing wrong? (Not a checklist of things that might be wrong with the URL.)
Stewart
I’m confused
2
people have this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
The company marked this question as answered.
-
Inappropriate?It's not you it's the documentation! The good news is that we're about to release a shiny new version next week that addresses your requests.
I will be in touch personally in the meantime to give you individual support. -
Inappropriate?For posterity, here are some pointers which helped me, with Thor's help, in getting fastpass working:
1. If you are testing your site, and you are using the fastpass debugger provided by getsat in the admin area, use two different browsers. You can't be logged in as an admin for your site, and test an auto-login feature at the same time!
2. Use a cookie viewer to monitor what is happening with cookies at various stages of the click-thru, even if you are not using the cookie "method". There are several cookie plug-ins for Firefox available.
3. Be careful with customization of your getsat community. Javascript in your customization can break fastpass, so switch it off until you've got fastpass working.
4. The fastpass debugger will accept two formats of url. If ${URL} is the string returned by Fastpass.url(...) then fastpass debugger accepts:
a. ${URL}
b. http: / / getsatisfaction.com/my_community?fastpass=${ENCODE(URL)}
For option b., the URL must be url_encoded; for option a. it must not be.
5. For the cookie method to work, you need CNAME enabled. If you don't have CNAME, use the direct url or script method.
6. The url generated by Fastpass.url(...) is used by both the direct url and the script method. The url returns a javascript file. The direct url method uses format from 4.b. above.
7. The script string returned by Fastpass.script(...) is javascript which, in the browser, adds two <script> tags to the <head> of the document. The first <script> is a fastpass common js library. The second <script> is that mentioned in 6. above. If you like, you can put into your HTML the following:
<head>
<script id="fastpass_common" type="text/javascript" src="http://getsatisfaction.com/javascripts/fastpass.js"></script>
<script id="fastpass" type="text/javascript" src="${URL}"></script>
</head>
This has the same effect, and you can then use GSFN.goto_gsfn() in your href anchors.
8. The url constructed by Fastpass.url(...) is exact, for example, the sequence of the querystring args should not be changed, or constructed with your own OAuth library.
9. When using the fastpass debugger, don't add a trailing CR/LF to the url, or the debugger will barf.
10. FINALLY, and most vitally, FASTPASS IS NOT OAUTH!
The documentation here: http://getsatisfaction.com/developers...
has absolutely nothing to do with the documentation here: http://getsatisfaction.com/developers... or here: http://getsatisfaction.com/developers....
Do not try to understand fastpass in terms of OAuth (see 8. above)
Stewart
I’m confident
1 person says
this answers the question
1 Comment Add a comment
This answers the question
-
Thanks for the crib sheet, Stewart! We'll be integrating your feedback into our next revision of the FastPass documentation.
EMPLOYEE
