Can't properly update APNS credentials on Notification Hub

Ben K 61 Reputation points
2023-03-09T22:29:50.0566667+00:00

I am trying to update the APNS credentials for several notification hubs my company has in Azure Portal. I have generated the new .p12 certificate and given it a password, but when I try and upload the certificate, the following happens:

  1. In Azure Portal, I go to the notification hub's APNS credential section. It lists the old certificate's hash as the thumbprint: D1E7D736D688AAA11F4CCA7AE992D9C9F38E8A78.
  2. I upload the new .p12 file and enter the password. (I have manually checked the expected thumbprint of the new .p12 - its thumbprint, or rather its SHA1 hash, is AA670FE991683F95ED6500C7B81C656A40182D7C .)
  3. Upon clicking Save, Azure Portal says the notification hub was successfully updated, but the certificate thumbprint field does not change. It still has the old hash. I'm left to conclude that it didn't actually update anything.

This happens even if I delete the previous certificate and upload the new one afterward.

How do I fix this?

Azure Notification Hubs
Azure Notification Hubs
An Azure service that is used to send push notifications to all major platforms from the cloud or on-premises environments.
265 questions
{count} votes

Accepted answer
  1. SnehaAgrawal-MSFT 18,366 Reputation points
    2023-03-21T15:01:35.31+00:00

    Thanks for reaching here! Could you please double check that the new .p12 certificate is uploaded correctly and the correct thumbprint is entered and verify that the new .p12 certificate is in the correct format and has the correct password you may also try using the Azure CLI or Azure PowerShell to update the APNS credentials for your notification hubs.

    Let us know.


0 additional answers

Sort by: Most helpful