headless authentication Azure AD b2c

问题:

I am looking for a way to authenticate a user by username/password in a headless manner for Azure AD b2c. Azure AD b2c is great but we feel the redirects for logins can lead to confusion among customers (and sometimes even prevented by some browsers). Also we want to be in full control of the customers UX experience.

I have researched ADAL and the Graph API but have not found anything yet.

Gina

回答1:

It is not currently possible to run Azure B2C without an interactive user present. While I am sure it will arrive at some point, at present, you can't create back-end applications based on B2C.

According to the Azure Active Directory B2C preview: Limitations & Restrictions

Daemons / Server Side Applications

Applications that contain long running processes or that operate without the presence of a user also need a way to access secured resources, such as Web APIs. These applications can authenticate and get tokens using the application's identity (rather than a consumer's delegated identity) using the OAuth 2.0 client credentials flow. This flow is not yet available in Azure AD B2C preview - which is to say that applications can only get tokens after an interactive consumer sign-in flow has occurred.

回答2:

As mentioned here, you can use Azure AD Apps for the Client Credential Flow for Service Accounts. It is not optimal but it works.

1. Define an Azure AD App for the Web API
2. Define an Azure AD App per Service Account
3. Configure the Web API to accept tokens from your B2C Tenant and Azure AD
   • Assuming you alredy have your Web API configured for B2C...
   • The well-known configuration URL for the Azure AD App is https://login.microsoftonline.com/[your-b2c-tenant].onmicrosoft.com/.well-known/openid-configuration
4. Request an access token against the Service Account AD App for the Web API

Note: be sure to create the Azure AD Apps under your B2C Tenant.

---

Code Snippet to get an Access Token from C#

using (var httpClient = new HttpClient())
{
    httpClient.BaseAddress = new Uri("https://login.microsoftonline.com");

    var content = new FormUrlEncodedContent(new[]
    {
          new KeyValuePair<string, string>("grant_type", "client_credentials")
        , new KeyValuePair<string, string>("client_id", "[service account app id e.g. 10d635e5-7615-472f-8200-a81d5c87c0ca")
        , new KeyValuePair<string, string>("client_secret", "[client secret defined in the service account e.g. 5L2ZJOBK8GI1wRSgGFooHcBkAOUOj65lQd9DgJxQOrw=]")
        , new KeyValuePair<string, string>("scope", "[App ID URI of the web api azure ad app]/.default e.g. https://my-b2c-tenant.onmicrosoft.com/my-azure-ad-ap/.default")
    });

    var requestResult = await httpClient.PostAsync("/[your b2c tenant].onmicrosoft.com/oauth2/v2.0/token", content);
    var contentResult = await requestResult.Content.ReadAsStringAsync();

    var json = JObject.Parse(contentResult);
    var accessToken = (string)json["access_token"];
}

App ID URI

---

You will probably want to define some custom claim(s) to secure the Web API. See 'Application Permissions' here.

1. Modify the application manifest on the Web API Azure AD App

   {
       "appRoles": [{
               "allowedMemberTypes": [
                   "Application"
               ],
               "displayName": "Some display nane",
               "id": "[create a new guid]",
               "isEnabled": true,
               "description": "Allow the application to _____ as itself.",
               "value": "some-claim"
           }
       ]
   }
   

2. Grant the Service Account Azure AD App permission to the custom application permission(s) defined

The permissions granted to the service account will come back in the roles claim:

{
  "roles": [
    "some-claim"
  ]
}

---

Please upvote the user voice feedback item to make this easier :)

回答3:

If what you want is headless authentication, why don't you simply use Azure AD alone? It has an API. And if you intend to create and manage all the UI yourself, why would you want or need AD B2C?

回答4:

Azure AD B2C cannot offer headless authentication but combining custom journeys
vanity domains and custom styling its possible for users to never leave your site

回答5:

What you are looking for is OWIN's resource owner password credentials in azure AD b2c. You can refer https://feedback.azure.com/forums/169401-azure-active-directory/suggestions/13817784-add-support-for-resource-owner-password-credential and upvote for this feature to be implemented

回答6:

Still in preview (as of Jan 2018) but might be what you're looking for if you're using Azure Functions. Take a look at Microsoft Graph bindings for Azure Functions