dotnetopenauth

I'm using DotNetOpenAuth ( http://dotnetopenauth.net/ ) library to authenticate at linkedIn.com . I develop a desktop application and now I'm a little confused. I'm unaware if it's possible to authenticate using a desktop application. Does anybody know? If it's possible please show me how to do that. Yes, it depends on how you want to approach it, but maybe looking at the DesktopConsumer class in the API might point you in the right direction: http://docs.dotnetopenauth.net/v3.4/html/T_DotNetOpenAuth_OAuth_DesktopConsumer.htm One example usage as a desktop app is detailed here: http:/

On this line i am getting an exception - OAuthWebSecurity.CreateOrUpdateAccount(provider, providerUserId, model.UserName); System.Web.Security.MembershipCreateUserException: The username supplied is invalid. The data going into this is provider - "facebook" providerUserId - "1321311387573991" model.UserName - "Max Payne" The initialization works fine using WebSecurity.InitializeDatabaseConnection("club", "User", "UserID", "UserName", autoCreateTables: true); I cannot find any examples of why it says the username is invalid? Is there a criteria somewhere that defines what is a correct user name

I'm mildly familiar with DotNetOpenAuth and OAuth in general, but in terms of Web API development, what is the best way to lock down a web service in terms of the following criteria: Ease of implementation Interoperability/compatibility with end-user facing platforms (iOS, Android, Win Phone, Flex...) Whether or not it is clearly standards-based (like OAuth for example) Thanks! please take a look here: OAuth 2.0 in Web API Inside the WebApiContrib project there are also Basic Authentication samples which is straight forward but it should not be used without SSL. The DotNetOpenAuth .zip

Most (all?) OAuth resources - both information about the protocol and code libraries for easily using them in your own applications - one seems to find on the internet seem to assume the application you are using it in is a web application. I would however like to start using OAuth in my windows mobile Twitter client for interactions with Twitter where I now use Basic Authentication through a set of simple methods I hand rolled. If I'm correct, Basic Authentication is about to be deprecated by Twitter in June of 2010, so I have a hard deadline to keep my Twitter client working after this

I've build a ASP.NET MVC 3 (RC at the moment) site that uses OpenID login system. I was still learning about OpenID while implementing this so I commented the code heavily. The result is a site that let's users login/register with OpenID, add other OpenIDs to their account and also remove them. This little project can be then used as a starting point for any new project that would use OpenID login system. It can also be used as a resource for people to learn OpenID with. I decided to release this project as open source. This will be my first open source project and I need to decided what

I have the DotNetOpenAuth sample provider running locally and it appears to correctly handle requests via the web browser. I can step through the handler for authorisation in the debugger. I have a project which can authenticate with Google and other providers but fails with the sample provider. The sample provider never sees a request at all and the relying party throws an exception complaining No OpenID endpoint found. Say I do the following in the relying party: string providerURL = "http://localhost/openid/provider"; // Now try the openid relying party... var openid = new