Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ServiceBus] Support SAS token-via-connection-string auth, and remove ServiceBusSharedKeyCredential export #13627
[ServiceBus] Support SAS token-via-connection-string auth, and remove ServiceBusSharedKeyCredential export #13627
Changes from 2 commits
e666f57
ac20634
902f92d
d1062f6
892b612
e05c349
f3b51fb
f8d8ad1
f83bf4c
df456b6
7937c8f
1934db9
c7ee6f2
78486e7
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not super confident on
large number
being implemented astime.time() * 2
.Have we tested this case -- no expiry provided in signature and we default to a very large number?
The concern I have here is that as you know our uamqp is built upon C, whether this would lead to integer overflow on certain platforms, making expiry being some negative value.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wisdom beyond your years. My inclination would be to use some vestige of INT_MAX. I'll poke around, but shout if you know off the cuff the incantation that I want to properly align with whatever is being done in the AMQP level.
(Worded more clearly; will I be shooting myself in the foot if I use sys.maxint as far as you know of uamqp?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Per our OOB discussion: Writing this test ended up exposing the following uamqp bug
Added issue for future investigation, noting this in the test stub that we can reenable once it's fixed.