Unanswered

unauthorized when sending to service bus

(0) Share

Report

Posted on by jatwork

Get the following when trying to send a simple message to a service bus queue

40103: Invalid authorization token signature, Resource:sb://<namespace>.servicebus.windows.net/removed. TrackingId:<removed>, SystemTracker:<removed>.servicebus.windows.net:<removed>, Timestamp:2/12/2018 8:43:02 PM clientRequestId: <removed>

This has been working fine, but stopped a couple weeks ago. I do go to the azure portal and grab the shared access policy connection string for the root namespace, i.e. not for a specific queue.

Categories:

Building flows

I have the same question (0)

All responses (2)

Answers (0)

v-xida-msft on at

Like (0)

Report

Hi @jatwork,

Could you please share a screenshot of your flow's configuration?

Do you use the "Send message" action of Service Bus connector within your flow?

The user MarkStokes has faced similar issue with you and the Microsoft Employee SameerCh has made a response to it. Please check the response the Microsoft Employee SameerCh has made within following thread:

https://powerusers.microsoft.com/t5/Connecting-To-Data/Service-Bus-Connection-String/td-p/3417

In addition, please check and see if the following article would help in your scenario:

https://social.msdn.microsoft.com/Forums/en-US/8aad223c-d299-4a1f-8eb4-3d4000a2b5ad/40103-invalid-authorization-token-signature-error-registering-to-notification-hub?forum=winappswithhtml5

Also please take a try to re-create a connection to the connector and re-create your flow to check if the issue is solved.

Best regards,

Kris

Was this reply helpful? Yes No
jatwork 2 on at

Like (0)

Report

When I retested I am geting the same error.
I was already following the other discussion and am taking the root namespace connection string for the service bus.
Can you try it on your side and see if you get an error.
Here is a screen shot:

Button-> Compose with {"name":"myname"} ->send to Service Bus
thanks,
Jonathan

Was this reply helpful? Yes No