Loading Profile...
How can I get FastPass to work
I'm trying to get single sign on to work. I've attempted all the methods: javascript, cookie, and even plain query string link, but it does not seem to do anything. In the simpliest form I click the "Our Support Community" link with the embeded url in the query string that I created on my site and start to ask a question or try to login/signup, but there's only a prompt for username/password. The fastpass url seems to be valid in all cases, but when I actually try it out nothing works. Here are the instructions I'm following: http://getsatisfaction.com/developers... (everything installed fine). I'm trying to test this on my local development machine which I have mapped to carl.mixamo.com (hosts file). Our support site is community.mixamo.com.
I’m frustrated
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?Hi Carl,
Sorry you're having trouble. Give me a call at 415.205.0115 and I'll see if I can help you through this. -
Inappropriate?Thanks for the help on the phone Thor, changing the DOMAIN field to community.mixamo.com worked, but only for the link method. It doesn't seem to work when I set the fastpass cookie. When I look at the HTTP requests, I can see the cookie get destroyed when I navigate to our get satisfaction site. Does the user have to navigate to the get satisfaction from a link on our site with the fastpass in the query string?
I’m undecided
-
Inappropriate?I'm still having troubles with FastPass. Even passing the fastpass url thru the query string doesn't always work. Not sure what I'm doing wrong. Once the URL is generated do I have to use the same one or can it be re-generated on every call? Is there a problem with using all the different methods (cookie vs query string vs javascript)? Can I use letters in the unique id? Please help.
Carl
I’m frustrated
-
Inappropriate?Sorry, Carl, that this has been a problem. I'll try to get you some more help.
-
Inappropriate?Hi Eric,
It is taking us over 3 days to implement something that you guys say should take no more then few hours. We would really appreciate some attention to this issue. Thanks a lot!
I’m frustrated
1 Comment
Add a comment
This answers the question
-
I'm doing the best I can, matt. -
Inappropriate?Matt,
do you have a staging server I can see? I'm not clear from the description what is failing, and under what circumstances. But to answer your questions:
- The URL should be the same for each user once it's generated. No need to re-render
- Re: methods, there should be no reason you couldn't use more than one, though it's not recommended just because it seems like unnecessary extra work.
You can also see a good example of FastPass in action at http://Songkick.com (requires registration). They use the query string method.1 Comment Add a comment
This answers the question
-
And yes, the uniqueID is not picky about letters vs. numbers.
-
Inappropriate?Alright, I'm not sure what happened, but it looks like it's working now. Both in the query string method and in the cookie method. I also tested the Feedback widget and it looks like it works, but the username and email fields are blank with just edit boxes next to them.
I’m happier
2 Comments Add a comment
This answers the question
-
I'll take a look at fastpass in the widget to see if there are any gotchas there.
-
Hi Thor, Were you able to find the solution to the widget / fast pass problem? Thanks!
-
Inappropriate?Matt, we have a new release of the login component for widget getting deployed tonight. I expect this will fix the issue you're seeing. Thanks!
-
Inappropriate?New release did not fix it. In fact it made it much worse. Feedback widget used to work yesterday, but username and email fields where not populated. Today it just doesn't work, period.
Come on, guys, we are a paying customer -- can we get some attention here?
I’m frustrated
-
Inappropriate?Hi Matt, that's obviously frustrating. We tested this before release, but it sounds like there's a bug that surfaced in your situation. Do you have this on a page we can view?
-
Inappropriate?Hi Matt, I've reproduced the bug you reported, which partially disables the continue button in the Fastpass login flow. We introduced this bug last night as part of the new login component for the widget. We are working on a fix as we speak. Many apologies for the hassle.
-
Inappropriate?We released a fix that resolves the problem you were seeing, Matt. Thanks for reporting it, and again, apologies for the frustration.
Let me know if you have any other issues.
1 person says
this answers the question
-
Inappropriate?Thanks a lot, Thor! While we are still doing some testing, things seem to work on our end now. Really appreciate super fast turnaround with the bug fix release.
I’m thankful
EMPLOYEE
EMPLOYEE
