Closed PalmEmanuel closed 3 years ago
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @jfggdl, @axisc.
ServiceBut team, please help to look into this question.
Is there an update on this issue? I also ran into a similar issue.
This has been open for six months! It doesn't even have a milestone...
You have shipped a "feature" that doesn't work in any way, shape or form. Did you test the code at all?
Description
The SAS token for Azure Service Bus generated by New-AzServiceBusAuthorizationRuleSASToken is not valid for use.
Steps to reproduce
Create a Service Bus Namespace in Azure, together with a Queue. Create a SAS policy in the queue, and attempt to create a token using New-AzServiceBusAuthorizationRuleSASToken.
This results in:
According to the documentation,
se
needs to be in Unix time, andskn
should be the name of the policy, not the name of the key. For some reason it also comes with a space in the start of the token.Attempting to use it in the header will result in an error 401, subcode 40103 - Invalid authorization token signature.
Below is one of the ways I attempted to use it.
Creating my own token using the code at https://docs.microsoft.com/en-us/rest/api/eventhub/generate-sas-token#powershell as base works much better.
Environment data
Module versions