Updated resource provisioning script with creation and assignment of Oauth roles associated with app registrations governing our function app and static website

Author: hvalfangst

README.md

@@ -6,6 +6,9 @@ Once the CSV has been uploaded to the storage blob, another, blob-triggered Azur
 The computed statistics are then stored in a new blob container, which is used to serve the results to the user.
 These two functions are defined in the python script [function_app.py](hvalfangst_function/function_app.py) - which is the main entrypoint of our Azure Function App instance.
 
+The SPA is protected with Oauth2.0 authorization code flow with PKCE and OIDC. The user is redirected to the Azure AD login page, where they must authenticate before being redirected back to the SPA.
+
+
 The associated Azure infrastructure is deployed with a script (more on that below).
 
 A branch-triggered pipeline has been set up to deploy our code to the respective Azure resources using a GitHub Actions Workflows [script](.github/workflows/deploy_to_azure.yml). 
@@ -24,7 +27,7 @@ Thus, deploying the website is simply a matter of uploading the static files to
 
 ## Allocate resources
 
-The shell script [allocate_resources](infra/allocate_resources.sh) creates Azure resources using the Azure CLI and a
+The shell script [allocate_resources](infra/allocate_resources.sh) creates Azure resources using the Azure CLI in conjunction with a
 [Bicep](https://learn.microsoft.com/en-us/azure/azure-resource-manager/bicep/overview?tabs=bicep) template [file](infra/main.bicep). 
 
 It will create the following hierarchy of resources:
@@ -47,6 +50,26 @@ graph TD
     B -->|Contains| F
 ```
 
+## Registrations
+In addition to the resources listed above, the script will also create a **service principal** and two Microsoft Entra ID **app registrations.** 
+
+### Service Principal for GitHub Actions
+The service principal has been assigned contributor role to our resource group, which is sufficient in order to deploy the static web app to the storage blob.
+It has been assigned a federated credential configured to work with this repository as it is utilized in our CI/CD [GitHub Actions Workflow script](.github/workflows/deploy_to_azure.yml).
+
+### App Registration for Azure Function App
+
+Exposes the scopes **Csv.Writer** and **Csv.Reader** under URI **api://hvalfangst-function-app**
+
+![img.png](images/img.png)
+
+### App Registration for SPA
+
+Has a redirect URI configured to the static web app's URL and the permissions **Csv.Writer** and the OIDC ones.
+
+![img_1.png](images/img_1.png)
+
+
 ## GitHub secrets
 Four secrets are required in order for the GitHub Actions Workflow script to deploy the code to the Azure resources. 
 As may be observed in the [script](.github/workflows/deploy_to_azure.yml), these are:
@@ -56,4 +79,33 @@ As may be observed in the [script](.github/workflows/deploy_to_azure.yml), these
 - **AZURE_TENANT_ID**: Used to authenticate the service principal in order to deploy the static web app
 - **PUBLISH_PROFILE**: Used to deploy our two functions to the Azure Function App
 
-![img_1.png](images/img_1.png)
+![secrets.png](images/secrets.png)
+
+## Usage
+After provisioning resources, setting up secrets, and pushing the code to the repository, one
+may access the static web app by navigating to the following URL:
+
+```plaintext
+https://<storage_account_name>.z6.web.core.windows.net
+```
+
+You will be presented with the following.
+
+![img_2.png](images/img_2.png)
+
+Click on **Sign In** to initiate the OIDC flow - which redirects to the Azure AD permission consent screen.
+
+![oidc.png](images/oidc.png)
+
+Clik on **Accept** to be redirected back to the SPA, where you will be greeted with the following.
+
+![authenticated_user.png](images/authenticated_user.png)
+
+Proceed to click on **Upload** to choose a file to upload. Pick the CSV file named [input](input.csv) which has been provided for this purpose.
+
+![img_5.png](images/img_5.png)
+
+![img_6.png](images/img_6.png)
+
+The file name will be displayed in the input field. Click on **Upload** to attempt to upload the file to the storage blob.
+