locked
Upload failed. The new certificate must use the same subject CN as your previous certificate. RRS feed

  • Question

  • Hi,

    Updating expired certificate for Push Notification Service responds with "Upload failed. The new certificate must use the same subject CN as your previous certificate." message.

    I am trying to update our expired certificate with renewed valid one, which has the same CN, for Push Notification Service but I keep getting the above error message.

    How To replicate:

    • Create a new app
    • In the Services section, click on Push Notification
    • Under Microsoft Push Notification Service (MPNS) section, upload an expired certificate
    • Click on "Register", does not work
    • Click on "Renew Certificate" and drag and drop valid certificate with the same CN
    • It will give error message "Upload failed. The new certificate must use the same subject CN as your previous certificate."

    Thanks,

    Abhishek

    Friday, August 7, 2015 4:54 PM

All replies

  • Please provide the App Id.

    thanks, palash biswas [MSFT]

    This posting is provided "AS IS" with no warranties and confers no rights.

    Friday, August 7, 2015 11:36 PM
  • App Id are ec7d75b9-0af9-48e9-bc77-585251ea2ac4 and 475a4edf-9260-448b-994a-1bcdf455916b

    Abhishek



    Monday, August 10, 2015 9:01 AM
  • Hi @palash.biswas, Any update on this?


    Abhishek



    Tuesday, August 11, 2015 12:42 PM
  • "66 8c ... a4 d0" - is this the thumbprint of the new cert you are trying to upload?

    thanks, palash biswas [MSFT]

    This posting is provided "AS IS" with no warranties and confers no rights.

    Wednesday, August 12, 2015 12:49 AM
  • Yes @palash.biswas, that is correct.

    Abhishek

    Wednesday, August 12, 2015 8:17 AM
  • could you please try now? please let us know if you are still having the issue.

    thanks, palash biswas [MSFT]

    This posting is provided "AS IS" with no warranties and confers no rights.

    Wednesday, August 12, 2015 6:13 PM
  • Hi @palash.biswas ,

    The old certificate was remove from AppId:475a4edf-9260-448b-994a-1bcdf455916b and I updated with the new certificate. It is now working but only randomly. Its a 50/50 chance that  the notification comes through to the device. When ever it doesn't come through i get an 403 Forbidden exception.

    This is happening when our app is installed on Windows Phone 8.1 and works fine on Windows Phone 8.0.

    Could you also remove the expired certificate "66 8c ... a4 d0" from appIdec7d75b9-0af9-48e9-bc77-585251ea2ac4. This is our beta test app .

    Regards,

    Abhishek


    Abhishek




    Thursday, August 13, 2015 12:58 PM
  • Hi @palash.biswas  any update in this?

    This is where we are at:

    1. Updated AppId:475a4edf-9260-448b-994a-1bcdf455916b with new valid certificate

    2. Still can't update certificate for appId: ec7d75b9-0af9-48e9-bc77-585251ea2ac4.

    3. Push Notification on the updated app (AppId:475a4edf-9260-448b-994a-1bcdf455916b) not working properly. Works sometimes and when it doesn't work, it returns with 403:Forbidden error

    4. I checked Microsoft Trusted Root Certificate Program (http://social.technet.microsoft.com/wiki/contents/articles/31634.microsoft-trusted-root-certificate-program-participants.aspx) and "Go Daddy Root Certificate Authority – G2" which our certificate authoriser is part of that list (Thumbprint: 47BEABC922EAE80E78783462A79F45C254FDE68B)

    Regards,

    Abhishek


    Abhishek

    Friday, August 14, 2015 2:16 PM
  • Removed expired cert from 9NBLGGH1D3B7 (GO BETA).

    thanks, palash biswas [MSFT]

    This posting is provided "AS IS" with no warranties and confers no rights.

    Friday, August 14, 2015 8:37 PM
  • Hi Palash,

    I am Abhishek's colleague, we are looking for an update regarding point 3: Push Notification on the updated app (AppId:475a4edf-9260-448b-994a-1bcdf455916b) not working properly.

    Push notifications are sometimes received on a Windows Phone 8.1 device without issue but other times we receive back a 403 - Forbidden from the same device.

    Could you investigate this and if possible provide the reasons why we get this error intermittently?

    Regards

    Lance

    Monday, August 17, 2015 11:01 AM
  • Hi @palash.biswas  any update?

    Abhishek

    Wednesday, August 19, 2015 9:44 AM