All Apps must authenticate through the App Store OAuth2 Authorization Server.
[https://tools.ietf.org/html/rfc6749|OAuth 2.0) is an IETF specification that allows 3rd party applications to gain limited access to an HTTP service on behalf of a user.
OAuth is used extensively on the web already: if you have ever logged into a 3rd party web site using your Facebook, Google, or LinkedIn account, you have already used OAuth. Indeed, the App Store allows users to log in via LinkedIn, and then requests information such as a user's name, email address and profile picture to allow it to create a profile for the user, likewise with ADFS , and with Google accounts.
The App Store also has its own OAuth service, to allow applications such as the Valve Signature Tool to log users in via the App Store, and to allow those applications to charge users for application usage.
Below is a simple example illustrating the Authorization Code Grant Flow recommended for Web-Server Apps. Note the process is different for Excel, browser-based and other types of App.
There are a number of OAuth2 helper libraries available (depending on your development platform), however the example below considers a basic manual approach.
In order to use the App Store OAuth service, an application must be registered with the App Store.
When registering your App, you are asked to provide one or more valid Redirect URIs. The Authorization Server will only respond to HTTP requests from registered URIs. This helps prevent Man-in-the-Middle attacks.
Since the HTTP request carries secure information, we also stipulate all requests are from secure HTTPS sources.
Upon App registration, you are assigned an Application Id and Secret Key. The Application Id is considered public information. It composes part of the URL request to the App Store Authorization Server and can easily be identified by the user.
The Secret Key, however, must remain confidential. It should only be used server-side (i.e not in the web-browsing client). If a deployed app cannot keep the secret confidential, then an alternative grant flow must be considered.
Your registered App is given a status. Be sure this is not active until you are satisfied it is fully tested. Once an App is “Active” attempts debit requests are treated as genuine and transactions are processed.
OAuth permissions are known as scopes, and are used to control which information about a user an application can access, or restrict the actions that the application can perform on behalf of a user.
When a user is prompted to log into a web site via an OAuth service, the scopes are explained to the user so that they can decide whether or not to proceed. For example, when logging into the App Store via LinkedIn, a user is informed that the App Store will be able to access profile information including the user's email address, profile picture, and the industry that they work in.
The App Store's OAuth service currently supports 3 scopes:
Applications are not obliged to ask for access to all of the above scopes; they can pick and choose the scopes that they require.
In your App, create a “Log In” link sending the user to:
The link resolves to a log-in prompt, requesting the used log-in via LinkedIn, then authorize the Apps scope request.
If the user clicks “Allow,” App Store redirects the user back to your site with an authentication code.
The Authentication Code should not be returned to the app user. In the “Authorization Code Grant Flow”, it is the responsibility of your server-side code to then request the Authentication Code be exchanged for an access token. Note this request contains the Secret Key parameter.
POST https://appstore.intelligentplant.com/AuthorizationServer/OAuth/Token grant_type=authorization_code& code=AUTH_CODE_HERE& redirect_uri=REDIRECT_URI& client_id=CLIENT_ID& client_secret=CLIENT_SECRET
The server replies with an access token
Now that you have an access token, you can make requests to the App Store API.
When an application logs a user in via an OAuth service, they receive an access token for the user, also known as a bearer token, as well as information about when the access token expires, and (possibly) a refresh token that can be used to retrieve a new access token when the old one expires, instead of requiring the user to explicitly log into the application again.
The token contains embedded information about the user, and is signed and encrypted by the OAuth service so that only the machine that issued the token can authenticate requests made using the token. When an HTTP request is authenticated using a bearer token, a `ClaimsIdentity` object is assigned to the OWIN request object that contains all of the claims that were embedded in the token.
To authenticate requests made to the App Store API, the calling application must include a valid access token in the HTTP headers of the request. The token is specified using the `Authorization` HTTP request header, using the `Bearer` authentication scheme. For example:
var request = new HttpRequestMessage(HttpMethod.Get, "https://appstore.intelligentplant.com/api/resource/getuserinfo"); request.Authorization = new AuthenticationHeaderValue("Bearer", "my_access_token"); var response = await httpClient.SendAsync(request, someCancellationToken).ConfigureAwait(false); ...