BYOIP - CustomerSignatureNotVerified

PatrickK-4189 0 Reputation points
2023-08-25T09:11:09.1533333+00:00

Hello,

I want to add a custom /48 IPv6 Prefix for using in Azure Cloud, but I'm not able to validate the Prefix in Azure Portal. I tried several times and followed the guide (https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/create-custom-ip-address-prefix-portal), but I still get the error message: "CustomerSignatureNotVerified"

I checked the signedMessage several times and I'm able to verify the message using openssl and the certificate from whois, but Azure provisioning still throws the Error message above.

I also tried to delete everything and start again, but this leads to the same issue.

Does anyone have an idea what I did wrong?

Thanks
Patrick

Azure Virtual Network
Azure Virtual Network
An Azure networking service that is used to provision private networks and optionally to connect to on-premises datacenters.
2,778 questions
{count} votes

1 answer

Sort by: Most helpful
  1. GitaraniSharma-MSFT 50,096 Reputation points Microsoft Employee Moderator
    2023-08-28T03:01:42.7066667+00:00

    Hello @PatrickK-4189 ,

    I understand that you want to add a custom /48 IPv6 Prefix in Azure but you were not able to validate the Prefix in Azure portal and getting the following error message: "CustomerSignatureNotVerified".

    The following may be the causes for CustomerSignatureNotVerified Error:

    • If you have whitespace or carriage returns in the SignedMessage that you used to sign with your private key. Please verify this is not the case.
    • If you uploaded the wrong public key to your RIR or the key has whitespace in it.

    Refer: https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/create-custom-ip-address-prefix-portal#certificate-readiness

    You already checked both possible problems multiple times and you could verify your signed message by using the certificate from the whois record and the data submitted in Azure Portal. Openssl also reports "Verified OK".

    So, I requested you to send us an email for further troubleshooting. But you tried again and it worked this time. Even though you didn't change anything, the same commands worked and your issue is now resolved.

    It could have been a transient issue which was resolved automatically after some time.

    Kindly let us know if you need further assistance on this issue.


    Please "Accept the answer" if the information helped you. This will help us and others in the community as well.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.