Some thoughts on Authentication

I am working with you library and noticed that in the Desktop Authentication there is no way to prevent the URL from being launched -- have you given any thought to making this a conditional execution -- maybe based on a boolean property?

I am also curious if you would consider the same type of request for the UsernamePasswordAuthorization class -- allowing a property to be set to indicate if the password prompt should be used or not.

The reason behind the requests is that I am looking to create a non-interactive background application (windows service and or WCF service) and both of these features require user interaction.

I noticed you might be thinking along these lines with one of the more recent checkins which includes the MvcOAuthAuthorization -- the only issue with this is that it breaks my build as I do not have Mvc installed.

So the problem with this is the it means the library can only be used in an application that is running interactively -- what about running as an NT service in the background or in a WCF call or in an ASP.NET server control. Non of these can display
a windows forms dialog which is what the Kerr library seems to be doing.

Since it is possible to pass in credentials, am was a little surprised to see that the library provided this functionality. What about providing an event that the call can subscribe to and implement their own "request for password".
That way it can be retrieved from anywhere (data store, data base, user, etc).