Remove SAS dependency for Data Protection blob access

[DrizzlyOwl]

Why do we need this?
The data protection keys were previously uploaded to Azure Storage as a Blob, using a Connection String that is expected to have a valid SAS Token appended to it. If that SAS token expires then the app will not have the ability to rotate/refresh the keys in Storage.

Without the ability to update the or access the key in the Blob Storage, the containers will get out of sync if there is more than 1 instance of the app running in a load balanced configuration.

What does this change do?

• Deploys a 'File Share' that is shared between all containers. This is mounted at /srv/app/storage.
• Change the Data Protection method to use the Local Filesystem (where the file share is mounted)
• • This means that all replicas of the app can share the same key
• Deployed a Key Vault that contains a Cryptographic Key which will encrypt the master data protection key at rest.
• If the Key Vault Key is supplied to the app, then the Data Protection keys will be encrypted at rest

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud