If I don't I would like to present a partial view to the user with some basic questions etc.. So it seems that this is not possible since the redirect kills any chance of getting data back to the original page. Process bullets as requested: Dot Net Open Auth supports both approaches, but of course there is plenty of code in the controller and view, external to the library, that you have to write.
I do have a sample that demonstrates a relatively polished #2 implementation.
The name of the view should be the same as the one used in the The idea here is to reload the partial view on the page when the user selects a different category from the drop down list.
They allow you to update only a part of the DOM without having to perform a full page refresh or a postback.
Using this approach, the controller can push a nice object model back to the partial view instead of Json and we can take advantage of Razor and/or scaffolding for data presentation while enhancing the whole user experience.
only using unobstrusive-ajax dint help in my application. This can help to get the content without reloading the entire page. I can't actually redirect to another View(redirect to other controller action and get to its View) but the partial page load works fine. Action Link("Add a Claimant", "Index", "Property", new Route Values().