I am considering the default default OAuth implementation that ships with asp.net mvc 4. This is definitely impressive since all I had to do was add this line to AuthConfig.cs:
OAuthWebSecurity.RegisterLinkedInClient("_key_", "_secret_");
By incorporating the above, they offered a LinkedIn link to enter. I was asked to enter the password once, but after entering I received:
"Error logging in. Unsuccessful login with the service."
and since then it has passed since w / out again the password is requested.
It is not clear to me if this is due to the initial bad credentials that I entered, or something with the way I set the key.
In addition, I do not see the actual controller code anywhere in my application, therefore, even if my login worked, it is not clear how I can get information from the linked in .. that is, the history.
Well, how easy was this integration, but am I leaning towards a more manual implementation of this?
However, I cannot help but wonder what is probably also working on the implementation.
UPDATE
I traced this problem as a call:
public ActionResult ExternalLogin(string provider, string returnUrl) { return new ExternalLoginResult(provider, Url.Action("ExternalLoginCallback", new { ReturnUrl = returnUrl })); }
the callback returns with "401 Unauthorized" .. even if the credentials are correct. what can I gather in other posts from, can this be due to malformed OAuth library headers?