Azure Service Bus - 401 40103: Invalid authorization token signature for post message using CURL
I see Authorization failure while posting a message to a queue I created in Azure Service bus using CURL
Command:
curl -v -X POST -H 'Authorization: SharedAccessSignature sig=58ecf57a25352fb4506f6a934bace10eeac4dae8eaf578093b8161af949b7ef4&se=1543536196&skn=test&sr=https%3A%2F%2Fndasns.servicebus.windows.net%2Fasbqueue' -H 'Content-Type: application/vnd.microsoft.servicebus.yml' https://ndasns.servicebus.windows.net/asbqueue/messages -d '[{"body":"m1"}]'
namesapce name: ndasns
queue name: asbqueue
I used
https://www.freeformatter.com/hmac-generator.html#ad-output
to create signature of my resource uri using secretkey, resource uri and token expiration time. Below captures the input i provided.
https://ndasns.servicebus.windows.net/+"n"+1543536196
I chose token expiry time as some time of 30th November 2018
I have created a new shared access policy for my queue called test which has all three: send, receive, Manage rules enabled.
The output of the CURL command is as shown below:
HTTP/1.1 401 40103: Invalid authorization token signature
I followed below link to frame my sendMessage
https://docs.microsoft.com/en-us/rest/api/servicebus/send-message-batch
and below link to create SAS token
https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-sas
Is there any way I could debug this error further?
azure authentication curl azureservicebus asked Nov 20 '18 at 21:48
Anitha
46115
add a comment |
I see Authorization failure while posting a message to a queue I created in Azure Service bus using CURL
Command:
curl -v -X POST -H 'Authorization: SharedAccessSignature sig=58ecf57a25352fb4506f6a934bace10eeac4dae8eaf578093b8161af949b7ef4&se=1543536196&skn=test&sr=https%3A%2F%2Fndasns.servicebus.windows.net%2Fasbqueue' -H 'Content-Type: application/vnd.microsoft.servicebus.yml' https://ndasns.servicebus.windows.net/asbqueue/messages -d '[{"body":"m1"}]'
namesapce name: ndasns
queue name: asbqueue
I used
https://www.freeformatter.com/hmac-generator.html#ad-output
to create signature of my resource uri using secretkey, resource uri and token expiration time. Below captures the input i provided.
https://ndasns.servicebus.windows.net/+"n"+1543536196
I chose token expiry time as some time of 30th November 2018
I have created a new shared access policy for my queue called test which has all three: send, receive, Manage rules enabled.
The output of the CURL command is as shown below:
HTTP/1.1 401 40103: Invalid authorization token signature
I followed below link to frame my sendMessage
https://docs.microsoft.com/en-us/rest/api/servicebus/send-message-batch
and below link to create SAS token
https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-sas
Is there any way I could debug this error further?
azure authentication curl azureservicebus asked Nov 20 '18 at 21:48
Anitha
46115
add a comment |
I see Authorization failure while posting a message to a queue I created in Azure Service bus using CURL
Command:
curl -v -X POST -H 'Authorization: SharedAccessSignature sig=58ecf57a25352fb4506f6a934bace10eeac4dae8eaf578093b8161af949b7ef4&se=1543536196&skn=test&sr=https%3A%2F%2Fndasns.servicebus.windows.net%2Fasbqueue' -H 'Content-Type: application/vnd.microsoft.servicebus.yml' https://ndasns.servicebus.windows.net/asbqueue/messages -d '[{"body":"m1"}]'
namesapce name: ndasns
queue name: asbqueue
I used
https://www.freeformatter.com/hmac-generator.html#ad-output
to create signature of my resource uri using secretkey, resource uri and token expiration time. Below captures the input i provided.
https://ndasns.servicebus.windows.net/+"n"+1543536196
I chose token expiry time as some time of 30th November 2018
I have created a new shared access policy for my queue called test which has all three: send, receive, Manage rules enabled.
The output of the CURL command is as shown below:
HTTP/1.1 401 40103: Invalid authorization token signature
I followed below link to frame my sendMessage
https://docs.microsoft.com/en-us/rest/api/servicebus/send-message-batch
and below link to create SAS token
https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-sas
Is there any way I could debug this error further?
azure authentication curl azureservicebus asked Nov 20 '18 at 21:48
Anitha
46115
I see Authorization failure while posting a message to a queue I created in Azure Service bus using CURL
Command:
curl -v -X POST -H 'Authorization: SharedAccessSignature sig=58ecf57a25352fb4506f6a934bace10eeac4dae8eaf578093b8161af949b7ef4&se=1543536196&skn=test&sr=https%3A%2F%2Fndasns.servicebus.windows.net%2Fasbqueue' -H 'Content-Type: application/vnd.microsoft.servicebus.yml' https://ndasns.servicebus.windows.net/asbqueue/messages -d '[{"body":"m1"}]'
namesapce name: ndasns
queue name: asbqueue
I used
https://www.freeformatter.com/hmac-generator.html#ad-output
to create signature of my resource uri using secretkey, resource uri and token expiration time. Below captures the input i provided.
https://ndasns.servicebus.windows.net/+"n"+1543536196
I chose token expiry time as some time of 30th November 2018
I have created a new shared access policy for my queue called test which has all three: send, receive, Manage rules enabled.
The output of the CURL command is as shown below:
HTTP/1.1 401 40103: Invalid authorization token signature
I followed below link to frame my sendMessage
https://docs.microsoft.com/en-us/rest/api/servicebus/send-message-batch
and below link to create SAS token
https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-sas
Is there any way I could debug this error further?
azure authentication curl azureservicebus azure authentication curl azureservicebus asked Nov 20 '18 at 21:48
Anitha
46115
asked Nov 20 '18 at 21:48
Anitha
46115
edited Nov 20 '18 at 23:39
asked Nov 20 '18 at 21:48
Anitha
46115
asked Nov 20 '18 at 21:48
Anitha
46115
asked Nov 20 '18 at 21:48
Anitha
46115
46115
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Changing the content of the sr parameter (namespace) of the Authorization header to just ndasns instead of https%3A%2F%2Fndasns.servicebus.windows.net%2Fasbqueue might solve the problem.
Hope it helps!
answered Nov 21 '18 at 7:00
Itay Podhajcer
1,839312
Tried with just ndasns for sr parameter. But still seeing the same error.
– Anitha
Nov 21 '18 at 19:50
You used SHA256 when you generated the signature?
– Itay Podhajcer
Nov 22 '18 at 5:13
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53402081%2fazure-service-bus-401-40103-invalid-authorization-token-signature-for-post-me%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Changing the content of the sr parameter (namespace) of the Authorization header to just ndasns instead of https%3A%2F%2Fndasns.servicebus.windows.net%2Fasbqueue might solve the problem.
Hope it helps!
answered Nov 21 '18 at 7:00
Itay Podhajcer
1,839312
Tried with just ndasns for sr parameter. But still seeing the same error.
– Anitha
Nov 21 '18 at 19:50
You used SHA256 when you generated the signature?
– Itay Podhajcer
Nov 22 '18 at 5:13
add a comment |
Changing the content of the sr parameter (namespace) of the Authorization header to just ndasns instead of https%3A%2F%2Fndasns.servicebus.windows.net%2Fasbqueue might solve the problem.
Hope it helps!
answered Nov 21 '18 at 7:00
Itay Podhajcer
1,839312
Tried with just ndasns for sr parameter. But still seeing the same error.
– Anitha
Nov 21 '18 at 19:50
You used SHA256 when you generated the signature?
– Itay Podhajcer
Nov 22 '18 at 5:13
add a comment |
Changing the content of the sr parameter (namespace) of the Authorization header to just ndasns instead of https%3A%2F%2Fndasns.servicebus.windows.net%2Fasbqueue might solve the problem.
Hope it helps!
answered Nov 21 '18 at 7:00
Itay Podhajcer
1,839312
Changing the content of the sr parameter (namespace) of the Authorization header to just ndasns instead of https%3A%2F%2Fndasns.servicebus.windows.net%2Fasbqueue might solve the problem.
Hope it helps!
answered Nov 21 '18 at 7:00
Itay Podhajcer
1,839312
answered Nov 21 '18 at 7:00
Itay Podhajcer
1,839312
answered Nov 21 '18 at 7:00
Itay Podhajcer
1,839312
answered Nov 21 '18 at 7:00
Itay Podhajcer
1,839312
1,839312
Tried with just ndasns for sr parameter. But still seeing the same error.
– Anitha
Nov 21 '18 at 19:50
You used SHA256 when you generated the signature?
– Itay Podhajcer
Nov 22 '18 at 5:13
add a comment |
Tried with just ndasns for sr parameter. But still seeing the same error.
– Anitha
Nov 21 '18 at 19:50
You used SHA256 when you generated the signature?
– Itay Podhajcer
Nov 22 '18 at 5:13
Tried with just ndasns for sr parameter. But still seeing the same error.
– Anitha
Nov 21 '18 at 19:50
Tried with just ndasns for sr parameter. But still seeing the same error.
– Anitha
Nov 21 '18 at 19:50
You used SHA256 when you generated the signature?
– Itay Podhajcer
Nov 22 '18 at 5:13
You used SHA256 when you generated the signature?
– Itay Podhajcer
Nov 22 '18 at 5:13
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53402081%2fazure-service-bus-401-40103-invalid-authorization-token-signature-for-post-me%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
