The wizard adds settings to you appsettings.json file and configures you startup class to use the B2C information you just entered.
Of course, you can adjust a lot more settings, but for our case, this is enough in the first place.Īfter you have created the policy, you can test it by clicking on the “Run Now” button and create a user for yourself. In our application, the configuration is as follows: Identity Provider Signup Attributes Application Claims Next, you have to enter information about the identity provider to use (in our case “Local Account”, the signup attributes (fields a user can enter during signup like “Given Name” and “Surname”) and application claims (information that will be sent with the identity token after login). It’s called “Sign-up or sign-in policy”.Ĭlick on the corresponding entry in the configuration blade and add a new one. To keep it simple, we only support local accounts at the moment.įortunately, we can create a policy that allows users to add an account and configure the login process in one single configuration. You can also add further identity providers like Google or Facebook to add social login capabilities to your application. In this example, we will only use “local accounts” (login with username and password).
AURELIA HTTP CLIENT EXAMPLE PASSWORD
You also need a policy to sign in and – if you want to – a policy to reset the password for a user. Next, to give users the ability to register for the application, you have to create a policy within the directory that allows users to create an account. Note down the Application ID and the domain name ( – in my case ), as we will need the values when we configure the authentication of our Web API. After a successful login, Azure AD will redirect the browser to that given URL.
In the reply URL enter “ because this is the URL our Aurelia app will be running on. Also, be sure to select “Include web app / web API”, because we want to use the “ implicit flow” as shown in the intro section above. Click “Add” and enter a name for the application. Therefore, go to the newly created B2C directory and select “Applications” in the settings blade. In my example, the configuration looks like that:Īfter the tenant is created, we have to add an application that can access the directory. Enter your desired organization and domain name and select the country/region you want the directory to be located. Search for “Azure Active Directory B2C” and select “Create” –> “Create a new Azure AD B2C Tenant”. Log in to your Azure account and select “New”. The creation of an Azure Active Directory is quite simple. Let’s start by creating the directory… Create a B2C Directory
The Aurelia app will login to the B2C directory via MSAL and use an ID token provided after a successful login to call the web API (authorization token in the request header). The B2C directory is the identity store where users of our application will be stored. In this example, we will develop a basic Aurelia frontend application, that will be secured via Microsoft Authentication Library (MSAL) for JavaScript backed by a custom Azure Active Directory (B2C). You will want to use a service like Auth0 or Azure Active Directory to handle authentication and/or authorization. These Controllers are quite specific on how they accept content.If you create a modern web application with an API / REST backend and a Single Page Application (SPA) as your frontend, that you want to run in the internet, you definitely don’t want to handle security / user management on your own. In ASP.NET 5, the WebAPI Controller is no longer the same as the WebAPI 2 Controllers we’re used to. A small post for my own reference, and yours if you need it.
0 kommentar(er)
