deployment.md

Deployment

1- First thing first: Fork the repository

👉 Fork this repository into your own account

To fork a GitHub repository click on the fork button on the top right of the screen. If you need more detail have a look to this GitHub doc: Fork a repo .

You will need to update the configuration (this document will explain when to do it and what to change), therefore it needs to be yours.

Make sure you are currently in YOUR GitHub repository.

2- Deploy AzUrlShortener (the backend)

This project is a frontend only so you will need to deploy the Azure Url Shortener in "headless mode". Do to it, click the blue button below and make sure to select none as Frontend

3- Deploy TinyBlazorAdmin (the frontend)

There are many ways you could run Tiny Blazor Admin website. In this deployment, we will use the new Azure Static Web App (SWA). However, because the TinyBlazorAdmin use Azure Active Directory (AAD), we need a standalone Azure Function (deployed at the previous step).

Open Azure portal (portal.azure.com), open the resource group where you created the backend (ex: streamDemo is our case). Click the "+" and search Static Web App, and click the Create button.

Note: You will need to Authorize Azure Static Web Apps, to have access to your GitHub repository (the one created when you forked the project). This is required because SWA uses GitHub Action to deploy.

Select your organization, repository and branch (ex: main).

Select Blazor as your Build Presets. The App location needs to be the location of the project file; in our case src/TinyBlazorAdmin/. The App artifact location can be left to wwwroot.

Note: We don't need the Api location, because AzURLShortener is deployed in a full standalone Azure Function.

Once it's all filled, click the Review, and create button. It will takes a few minutes to get deployed. During this time let's create and configure our security components.

4- Create Azure Active Directory (AAD) Components

Create AAD App for the Fontend

We need a Service Principal that we will use to authenticate our user to Azure Active Directory (AAD). To achieve this we will create an application registration in Azure.

From the Azure Portal (portal.azure.com), open the Azure Active Directory page. From the left option menu select App registrations, then create a new registration. Use a name that will help you to remember that it's for the TinyBlazorAdmin website (ex: TinyAdminApp) (1)

For the Redirect URL use Single-page application (SPA) (3) and enter the URL of the Azure Static WebApp deployed previously and add /authentication/login-callback. It should look lsomething like this:

https://bolly-tiger-04a15beef.azurestaticapps.net/authentication/login-callback

Note the ClientID and TenantID.

If you need to retrieve the ClientID and TenantID, they will be display at the top of the page once you select an app in the portal.

Go back in the Authentication and in the section Implicit grant check the checkbox Access Token and ID Tokens

Create App for the Azure Function

We need a second App registration, this time to let the Azure Function validate that user information contained in the token is valid.

From the Azure Portal, go to your Azure Function. From the left panel select the Authentication / Authorization (1) option. Enable the App Service Authentication (2) and click on Azure Active Directory.

1. Select Express.
2. Make sure Create New AD App is selected.
3. Give the AD App a name.
4. Click Ok.
5. DON'T FORGET TO CLICK THE SAVE BUTTON

Now, we need to configure the brand-new Ad App registration. Still from the Azure portal open the Active Directory blade. Select the App registration option from the left menu. Then select the application you just created.

1. From the left panel click the Expose an API option.
2. Click the Add a client application.
3. Enter the ClientID of the Frontend App (the first one created).
4. Check the Impersonation checkbox.
5. Save by clicking Add application.

Configure Backend and Frontend to Work Together

Now in your GitHub it's time to update the settings. The code needs to know the AD app to use and the Azure Function to call. Update those values inside TinyBlazorAdmin\wwwroot\appsettings.json

The Endpoint must ends with a /

{
  "AzureAd": {
    "Authority": "https://login.microsoftonline.com/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxxx",
    "ClientId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxxx",
    "ValidateAuthority": true
  },
  "UrlShortenerSecuredService": {
    "Endpoint": "https://__azFunction_URL__.azurewebsites.net/"
  }
}

Enabeling Cross-Origin Resource Sharing (CORS)

First we need the url of the caller (aka TinyBlazorAdmin). From the Azure Portal, open the TinyBlazorAdmin SWA blade. Note the URL display in the top right of the page this is the URL of your admin page.

Now we need to add this URL to the list in the CORS of the Azure Function that run AzUrlShortener. From the Azure portal open the blade of AzUrlShortener. From the left menu search CORS, and click it. Add the URL of the SWA and don't forget to save.

Try it!

Voila, the deployment is now completed. You can test it by creating a new short URL using the admin SWA.

Adding Custom Domain

To add a custom domain to your AzUrlShortener & TinyBlazorAdmin, follow these steps from the the AzUrlShortener repo.