Dear Open Hub Users,
We’re excited to announce that we will be moving the Open Hub Forum to
https://community.blackduck.com/s/black-duck-open-hub.
Beginning immediately, users can head over,
register,
get technical help and discuss issue pertinent to the Open Hub. Registered users can also subscribe to Open Hub announcements here.
On May 1, 2020, we will be freezing https://www.openhub.net/forums and users will not be able to create new discussions. If you have any questions and concerns, please email us at
[email protected]
I downloaded the newest version of DotNetOpenAuth and found only 3-legged OAuth is implemented in the sample projects.
In 2-legged OAuth, there's no user participation and no token is needed. Only the consumer key and the request signed by the consumer secret is sent to the provider. Does DotNetOpenAuth support 2-legged OAuth and is there any sample code?
There are no samples that ship with the library that demonstrate 2-legged OAuth as you say. But the library (intends to) support the scenario. When I last reviewed it, 2-legged OAuth seemed to work with DotNetOpenAuth. If you try it and find otherwise, please explain what's missing here: http://dotnetopenauth.net:8000/ticket/83
Oh, I have seen this page. But in DotNetOpenAuth, I can't send the request with empty token, otherwise, it will throw an exception. And TokenManager is a mandatory parameter for a web consumer. Since no token is needed for 2-legged OAuth, I don't know how DotNetOpenAuth supports it. I wonder if the enhancement in the 83
page is really implemented in DotNetOpenAuth.
This is great feedback, Montagne. Thanks for taking the time to give it. I'll investigate further.