Loading Profile...
questions about creating accounts via the API
Hi, we are thinking about integrating help center directly on our new website. I saw the post that said that you could enable an API key to create user accounts...
I have 2 questions about that:
Let's say we create an account for a user, do we automatically receive an access token/secret ? (so we can automatically login the user) or the user still has to grant us access after we've created his account?
And if a user that already has an account with getsatisfaction grants us access to post on his behalf, do we receive an access token/secret that we can store in our database? (I ask this because I've tested http://joby.com/support/helpstart.php and every time I login, it asks me if I grant them access!?)
Thank you very much!
I have 2 questions about that:
Let's say we create an account for a user, do we automatically receive an access token/secret ? (so we can automatically login the user) or the user still has to grant us access after we've created his account?
And if a user that already has an account with getsatisfaction grants us access to post on his behalf, do we receive an access token/secret that we can store in our database? (I ask this because I've tested http://joby.com/support/helpstart.php and every time I login, it asks me if I grant them access!?)
Thank you very much!
I’m excited
4
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.
-
Inappropriate?Hi Dan,
To your first question, the user still has to grant you access to their account. Which means that they would need to go to their email account to retrieve their default password. It is not an good solution, and we've worked out a different solution that will get unveiled in just a couple weeks. I don't think I'm at liberty to talk in detail about it, but the goal of the solution is to let users more easily post topics from a 3rd party site. It is out intention to continually improve the account integration problems we have, and I know we won't get it perfect with this next release, so I would love your thoughts about where we are falling down and how we can make it better.
As to your second question, it looks like that is a bug in the help center implementation. The access tokens do last, but it looks like help center uses session cookies instead of long lived cookies to remember your token. I'll forward this along to our consultant who built it and see if we can get that fixed. -
Inappropriate?Scott, do you have answer to this question? We're in the same boat and I just posted a variant of the same question...
http://getsatisfaction.com/getsatisfa...
I’m frustrated
-
Inappropriate?No, it hasn't been fixed yet. Our contractor just started a vacation, also, so unfortunately any sort of professional support from us is not available.
I would be more than happy to integrate a patch, if you are able to come up with a solution, but unfortunately I don't have the availability in my schedule to fix it myself.
While I've got you here, could I ask you why you chose Help center over using Get Satisfaction proper? I noticed that your install has no customizations, so I'm curious what made help center be your preferred choice?
Thanks, and sorry I couldnt be more helpful,
Scott -
Inappropriate?I can say that we choose Help Center because we personally have done a first pass of customization (http://alpha.loudcrowd.com/help/helps...) and have designs on several key things we want to alter about the flow.
But mainly it was about having a site that felt more a part of "us" than another service, which is precisely what the current registration flow (as well as the emails you receive) really breaks.
I'm hoping you guys can hop on this and help craft a solution. I've got a couple possible one's, but if no one has allocated time it's not really worth delving into.
EMPLOYEE
