• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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