BYOIP - CustomerSignatureNotVerified

Question

BYOIP - CustomerSignatureNotVerified

PatrickK-4189 0

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

GitaraniSharma-MSFT 50,096 Reputation points Microsoft Employee Moderator

2023-08-25T09:40:45.84+00:00
Hello @PatrickK-4189 ,

Welcome to Microsoft Q&A Platform. Thank you for reaching out & hope you are doing well.

I understand that you want to add a custom /48 IPv6 Prefix in Azure but you are 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

Regards,

Gita
PatrickK-4189 0 Reputation points

2023-08-25T10:03:03.6966667+00:00

Hello Gita,

thank you for your response. I already checked both possible problems multiple times, from my side there is no error, as written I could verify my signed message by using the certificate from the whois record and the data submitted in Azure Portal. openssl reports "Verified OK", therefore I can't find any issue and don't know why Azure is unable to verify it.

Regards,
Patrick
GitaraniSharma-MSFT 50,096 Reputation points Microsoft Employee Moderator

2023-08-25T10:33:25.77+00:00
Hello @PatrickK-4189 , We wish to engage with you offline for a much closer look, please send an email with subject line "ATTN gishar | BYOIP - CustomerSignatureNotVerified" to AzCommunity[at]Microsoft[dot]com with the following details, I will follow-up with you.

Reference this Q&A thread

Your Azure Subscription ID

The custom /48 IPv6 Prefix that you wish to add to Azure.

Note: Do not share any PII data as a public comment.

We will post a summarized answer once the issue is resolved.
PatrickK-4189 0 Reputation points

2023-08-26T09:54:19.53+00:00

Hello Gita,

I tried it once again and - although I didn't change anything - it seems to work now.

Just used the same commands as before.

Therefore my case is solved.

Anyway, thank you for your help.

Best Regards
Patrick
Muax Ja 0 Reputation points

2023-08-26T13:42:35.49+00:00

The error message "CustomerSignatureNotVerified" typically indicates that there's an issue with the verification of the signed message during the process of adding a custom IPv6 prefix in Azure. Since you've already followed the guide and verified the signed message using OpenSSL and the certificate from whois, it's puzzling that you're still encountering this error.

Here are a few troubleshooting steps you can consider:

Certificate Format and Encoding: Ensure that the certificate you're using is in the correct format (PEM or DER) and properly encoded. Azure has specific requirements for the certificate format.

Certificate Thumbprint: Double-check that you're using the correct thumbprint of the certificate during the process. Any mismatch here could result in the verification failure.

Clock Skew: Sometimes, clock synchronization issues between your local system and Azure can cause problems with certificate verification. Make sure your local system's clock is accurate.

Revocation: Azure might require access to certain CRL (Certificate Revocation List) URLs to verify the validity of the certificate. Ensure that your Azure environment can access these URLs without any restrictions.

Retry: Sometimes, issues can be temporary. Retry the process after a while to see if the problem persists.

Network or Azure Issues: Network glitches or issues on Azure's side could potentially cause verification failures. If possible, try from a different network or wait for some time before trying again.

Support: If you've exhausted all troubleshooting steps and the issue persists, consider reaching out to Azure support. They can provide more specific guidance and assistance in diagnosing the issue.

Documentation Updates: Occasionally, Azure documentation might be updated with changes or clarifications. Make sure you're referring to the most up-to-date documentation.

Azure Portal Bugs: While rare, there's also the possibility of a temporary bug or issue in the Azure Portal itself. Check if there are any recent reports of similar problems in the Azure community or forums.

Remember, debugging such issues can sometimes be complex due to the integration of different components. If you've double-checked everything and the problem persists, reaching out to Azure support might be your best course of action, as they can provide personalized assistance and investigate any potential technical issues on their end.
GitaraniSharma-MSFT 50,096 Reputation points Microsoft Employee Moderator

2023-08-28T03:00:30.9333333+00:00

Thank you for the update, @PatrickK-4189 .

Glad to hear that the issue is now resolved.

I've summarized the answer below for better visibility.

Please don’t forget to close the thread by clicking "Accept the answer" wherever the information provided helps you, as this can be beneficial to other community members.

1 answer

Your answer

GitaraniSharma-MSFT 50,096 Reputation points Microsoft Employee Moderator

2023-08-25T09:40:45.84+00:00

Hello @PatrickK-4189 ,

Welcome to Microsoft Q&A Platform. Thank you for reaching out & hope you are doing well.

I understand that you want to add a custom /48 IPv6 Prefix in Azure but you are 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

Regards,

Gita
PatrickK-4189 0 Reputation points

2023-08-25T10:03:03.6966667+00:00

Hello Gita,

thank you for your response. I already checked both possible problems multiple times, from my side there is no error, as written I could verify my signed message by using the certificate from the whois record and the data submitted in Azure Portal. openssl reports "Verified OK", therefore I can't find any issue and don't know why Azure is unable to verify it.

Regards,
Patrick
GitaraniSharma-MSFT 50,096 Reputation points Microsoft Employee Moderator

2023-08-25T10:33:25.77+00:00

Hello @PatrickK-4189 , We wish to engage with you offline for a much closer look, please send an email with subject line "ATTN gishar | BYOIP - CustomerSignatureNotVerified" to AzCommunity[at]Microsoft[dot]com with the following details, I will follow-up with you.

Reference this Q&A thread

Your Azure Subscription ID

The custom /48 IPv6 Prefix that you wish to add to Azure.

Note: Do not share any PII data as a public comment.

We will post a summarized answer once the issue is resolved.
PatrickK-4189 0 Reputation points

2023-08-26T09:54:19.53+00:00

Hello Gita,

I tried it once again and - although I didn't change anything - it seems to work now.

Just used the same commands as before.

Therefore my case is solved.

Anyway, thank you for your help.

Best Regards
Patrick
GitaraniSharma-MSFT 50,096 Reputation points Microsoft Employee Moderator

2023-08-28T03:00:30.9333333+00:00

Thank you for the update, @PatrickK-4189 .

Glad to hear that the issue is now resolved.

I've summarized the answer below for better visibility.

Please don’t forget to close the thread by clicking "Accept the answer" wherever the information provided helps you, as this can be beneficial to other community members.

Answer 1

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.

Share via

BYOIP - CustomerSignatureNotVerified

1 answer

Your answer