Allow for retrieval of access token.

[hazah]

Hey there, great lil bit of software, finding it very useful. Have you considered adding a way to retrieve the current access token so that it can be stored into the db? I'd be happy to contribute a function or two.

[inlet]

Thanks man! Well, haven't really considered storing the access token in the db.. I'm using Session instead. Any use case where storing in db comes in handy? .. just curious though :)
And of course feel free to contribute! Just fork it, love to see some contribution!

Kind regards

On 1 sep. 2011, at 18:28, hazah wrote:

Hey there, great lil bit of software, finding it very useful. Have you considered adding a way to retrieve the current access token so that it can be stored into the db? I'd be happy to contribute a function or two.

Reply to this email directly or view it on GitHub:
#1

[hazah]

In my case I'm developing the "login through linked in" button. Basically I already have existing users (via un/pw), and I'm mapping them to their linkedin accounts. Storing the tokens in the DB lets me identify the user in a similar manner that a username/password combo would once the authorization callback is called. If linkedin gives access to the oauth ID of that user, that would be a better field to store, as access tokens are really meant for single session type of use.

So far all I've done is allow myself to inject the access token manually into the component's session var, and so far it worked.

[inlet]

I think it's very specific, but again if you could make this more generic so that others can use it straight out of the box.. it would be awesome and I think a valuable addon as well! So please fork it and do a pull request :)

[hazah]

"Sign in with linkedin" is too specific? I'm not sure I follow. What do you mean?

[hazah]

I believe that I had been going about it the wrong way. I'm a little too used to the rails way of doing these things, so one of my assumptions were wrong.

I resolve that this is indeed not necessary for the function of signing in with linkedin, and that your module supports this type of query already. So I'm going to close this. Cheers, and thanks.