SSL Certificates Configuration
After You Renew or Install a Certificate
The following assumes you already installed and tested your certificate.
- Ensure that IIS can access the Certificate Private Key.
- Ensure that you update the Platform Domain or Accounts record (System Setup Section) with the Thumbprint for the Certificate in the OAuth Signing Certificate Thumbprint field.
- Ensure that you configured the IIS Site hosting MinistryPlatform to use the new or updated Certificate.
All of these steps must take place on the IIS Server that hosts MinistryPlatform. If your church is set up using multiple IIS servers, your exact steps may differ from this slightly.
Find your IIS User Account
Edit Permissions in MMC
Ensure Add User and Full Control
Get Certificate Thumbprint
Edit Platform Domain or Account Record
UPDATE dp_Domains SET OAuth_Signing_Certificate_Thumbprint = '{thumbprint}' WHERE Domain_ID = 1
Additional Steps
Check MinistryPlatform
Launch the Portal and Core Tools to ensure everything is still fully functional.
Add a Calendar Reminder About Expiration
This is not a critical step, but we recommend you do it. Add one or more reminders to your calendar for 14, 30, and 60 days before your SSL Certification expires to remind you that it will expire soon. Don't get caught without a valid SSL Certification. Not only is it a PCI violation, but it is not fun to change a certificate under pressure.
If your SSL Certificate is expiring soon or has expired, you'll see a reminder on your Customer Portal Dashboard.