• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Input ASP.NET Core Data Protection key store

Paul Hermans

Basic Pleskian
When hosting an ASP.NET Core application with Data Protection to encrypt and decrypt data, where do we store the key ring?

What are the options:
  1. Windows registry
  2. User profile (%LOCALAPPDATA%/ASP.NET/DataProtection-Keys)
  3. File system (i.e. C:\inetpub\vhosts\example.com\... )
Option 3 is the best option I think, this works with a default Plesk install, Keys will be backed up by Plesk Backup Manager and will be migrated when moving to another server etc.

But the documentation says the following:
"Use an X509 certificate to protect the key ring and ensure the certificate is a trusted certificate. If the certificate is self-signed, place the certificate in the Trusted Root store."

Where do we store this certificate? Plesk users do not have access to the Trusted Root store.

Link: Host ASP.NET Core on Windows with IIS
Link: Configure ASP.NET Core Data Protection

What do you think is the best way to protect the keys when using Plesk?
 
Back
Top