Sending Notification & Registering Device in Notification Hub

Europa Locks 5

Hi,

I am using Azure Notification Hub's REST APIs for registering devices (Android & iOS) & sending Notifications to it. I am intended to use them in Node JS API (written by me). Before that, I tried it on Postman and got 401 error having put the API url (https://europaNotificationHub.servicebus.windows.net/NotifyHub/registrations/?api-version=2020-06) Header: Content-Type: application/JSON, Authorization: Full Access Endpoint, x-ms-version: 2020-06. The body contains registration id: deviceToken, platform (gcm, fcm, apns, wns) & channelUri: deviceToken

When called from Postman, it gives a 401 unauthorized response code. Same happens in Node API (using axios).

Please provide a solution or suggestion over this.

B santhiswaroop naik 395 Reputation points

2023-07-04T18:18:48.2966667+00:00

The 401 unauthorized error indicates that the authentication credentials you provided for the Azure Notification Hub API are invalid or missing. To resolve this issue, you need to ensure that you include the correct authentication information in your request.

Here are a few steps you can take to troubleshoot and resolve the 401 unauthorized error:

Check Authentication Credentials: Double-check the authentication credentials you are using for the Azure Notification Hub API. The Authorization header should contain a valid authentication token or key. Make sure the token or key is correctly formatted and has the necessary permissions to access the Notification Hub.

Verify Endpoint: Ensure that the Full Access Endpoint you provided in the Authorization header is correct. It should be in the format Endpoint=sb://<namespace>.servicebus.windows.net/;SharedAccessKeyName=<keyName>;SharedAccessKey=<keyValue>.

Confirm API Version: Verify that the x-ms-version header you provided matches the supported API version for the Azure Notification Hub. Make sure you are using a valid and supported API version. You can refer to the Azure Notification Hubs REST API documentation for the correct API version to use.

Validate Content-Type: Check that the Content-Type header is set to application/json as you specified. Ensure that the request body you are sending is correctly formatted as JSON.

Inspect Error Details: If you are still experiencing the issue after checking the above points, examine the response body or error message returned by the API. It may provide additional details or error codes that can help identify the specific problem with your request.

Review Azure Notification Hub Configuration: Verify the configuration of your Azure Notification Hub, including access policies, namespaces, and associated resources. Ensure that your application or service has the necessary permissions to interact with the Notification Hub.
VenkateshDodda-MSFT 23,441 Reputation points Microsoft Employee

2023-07-05T09:32:23.7466667+00:00

@Europa Locks Thanks for reaching out to Microsoft Q&A, apologize for any inconvenience caused on this.

Based on the shared information, I have looked the backend logs of the notification hub(NotifyHub) and we see that the registration is failing with the error message Access denied. Not valid Authorization header value

As suggested by B santhiswaroop naik make sure that you are passing the entire value of DefaultFullSharedAccessSignature policy of your notification hub as an Authorization header while creating registration.

Feel free to reach back to me if you have any further questions on this.
Europa Locks 5 Reputation points

2023-07-05T12:24:21.2333333+00:00
Hi @B santhiswaroop naik , thanks for replying, I have gone through the steps you have provided. Those helped me a lot but still the error presists.

I am referring to this documentation https://learn.microsoft.com/en-us/previous-versions/azure/reference/dn223265(v=azure.100)

Check Authentication Credentials: Re-checked the Authorization Header. I am using the DefaulFullSharedAccessSignature key from AccessPolicy and for Request Header.

Verify Endpoint: As I've mentioned above I had directly copy-pasted the value from the azure portal itself so, I don't think that, this would be a cause.

Confirm API Version: The documentation mentions the version as 2015-01 and same is being used by me in the URL as well as x-ms-version in the Request Header

Validate Content-Type: The content-type mentioned is application/atom+xml;type=entry;charset=utf-8. Using the same in Request Header

Inspect Error Details: I get no response body in this case, only I can see is the postman's 401 Error Response Code

Review Azure Notification Hub Configuration: I have used the namespaces & Hub's name correctly from the portal, is there something I need to do like providing access to the requesting entity or something similar to that.

Also, here is the Request Body :

<?xml version="1.0" encoding="utf-8"?> <entry xmlns="http://www.w3.org/2005/Atom"> <content type="application/xml"> <GcmRegistrationDescription xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="https://schemas.microsoft.com/netservices/2010/10/servicebus/connect"> <GcmRegistrationId>device token goes here</GcmRegistrationId> </GcmRegistrationDescription> </content> </entry>

Please correct me, if I have gone wrong throughout in any part like, the body has something wrong in it or the other sections.

Appreciate your help. Thank You.
VenkateshDodda-MSFT 23,441 Reputation points Microsoft Employee

2023-07-06T08:20:37.0866667+00:00

@Europa Locks Thanks for sharing more information on this.

I wish to engage with you offline for a much closer look and provide a quick and specialized assistance, please send an email with subject line “Attn:Venkatesh|thread title” to AzCommunity@microsoft.com referencing this thread with your Azure subscription ID and Notification Namespace, Notification hub details, I will follow-up with you.

Share via

Sending Notification & Registering Device in Notification Hub

Your answer