Authenticate vs. Authorize

[hazah]

Hey again.

I Noticed that Linkedin has an authentication path using https://www.linkedin.com/uas/oauth/authenticate which is similar to the one already being utilized by this lib (https://www.linkedin.com/uas/oauth/authorize).

I think, if anything should be added to make this package complete, this might be it. I think there are valid contexts in which a user should not have to reverify their connection to a specific site (e. g. if its the only method of authentication). This would make it a one click deal. Interested? I wouldn't mind adding the function.

[hazah]

I already have this working for myself, this is about a 5 line addition to the component. Once you confirm I'll send in a pull request.

[inlet]

Now that sounds interesting! Could you do a pull request with the updated feature ?
Thanks in advance!

On 8 sep. 2011, at 15:29, Ivgeni wrote:

Hey again.

I Noticed that Linkedin has an authentication path using https://www.linkedin.com/uas/oauth/authenticate which is similar to the one already being utilized by this lib (https://www.linkedin.com/uas/oauth/authorize).

I think, if anything should be added to make this package complete, this might be it. I think there are valid contexts in which a user should not have to reverify their connection to a specific site (e. g. if its the only method of authentication). This would make it a one click deal. Interested? I wouldn't mind adding the function.

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

[hazah]

Well, I created a pull request. So this is moot now. I'm closing this thread so that discussion can be with the request.