This section provides an overview of what asp.net-web-api2 is, and why a developer might want to use it.

It should also mention any large subjects within asp.net-web-api2, and link out to the related topics. Since the Documentation for asp.net-web-api2 is new, you may need to create initial versions of those related topics.

Registering in an Android Application

These are the steps I've taken to log in / register using an Android app:

• Have a login activity which queries the ExternalLogins route, getting the available providers. This activity should have the NoHistory flag enabled and launch as a single instance.
• On a user's button press, launch a Custom Chrome Tab with the provider's URL. The user should be logged in and redirected back to your published site at the given return URL. Don't use a WebView.
• Have this page redirect the user again, using a custom URI scheme to launch a post-login activity within your application with the access token, expiry date and user account details added as additional data. This will need to be done in JavaScript on the web page, as the server's controllers can't access the URL parameters.
• Store the user's details and token in a local MySQL database. On each login, check to see if the token is still in date.
• Any calls to the API can now be authorized using the Authorization HTTP header, with your stored token added as so: “Bearer {token}”

Currently, Attribute Routes doesn't have Controller specific Message Handlers. As there is no way to specify Which handler to execute for which route at the time of declaration. This is possible in Conventional Routing.