Update README with instructions

README.md

@@ -44,3 +44,11 @@ You can populate the previously deployed storage accounts with blob containers a
 3. Run the following command:
 
 - `az deployment group create --resource-group <resource-group-name> --template-file <bicep-file-name>`, changing '<resource-group-name>' for the already deployed resource group name, and <bicep-file-name>` for /scripts/automation/modules/blob-container.
+
+### Generate client secret (App Registration) and inject to deployed key vault.
+
+1. Under /scripts/automation/appRegistration, there are vailable config files for each one of the environments (dev, staging and prod). Select which one you want to modify.
+2. Ensure that `CFG_IDA_CLIENT_ID` is the client ID of the App in which you want to add a new client secret. These values are already pre-filed for IDA app registrations.
+3. You can change `CFG_IDA_SECRET_NAME` by the secret name desired.
+4. Change `CFG_RESOURCE_GROUP` and `CFG_VAULT_NAME` for the resource group and respective key vault, in which the secret will be injected.
+5. Change the source in 'app-injection-secrets.sh' with the path to the config file you were editing and grat privileges to run it: `bash scripts/automation/appRegistration/app-injection-secrets.sh`

scripts/automation/appRegistration/app-injection-secrets-param-prod.cfg

@@ -2,7 +2,7 @@
 # Config file for prod environment
 # 
 # IDA-prod app registration
-CFG_IDA_CLIENT_ID=""
+CFG_IDA_CLIENT_ID="16df0336-e42b-45c6-a380-8f6fe66e1fa3"
 CFG_IDA_SECRET_NAME="AzureAd--ClientSecret"
 
 # Resource group and key vault name for key vault secret injection.

scripts/automation/appRegistration/app-injection-secrets-param-staging.cfg

@@ -2,7 +2,7 @@
 # Config file for staging environment
 # 
 # IDA-staging app registration
-CFG_IDA_CLIENT_ID=""
+CFG_IDA_CLIENT_ID="6f40ba9b-2029-400e-85e9-f1922cbf12c1"
 CFG_IDA_SECRET_NAME="AzureAd--ClientSecret"
 
 # Resource group and key vault name for key vault secret injection.