-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Merged
KieranBrantnerMagee
merged 14 commits into
Azure:master
from
KieranBrantnerMagee:kibrantn/servicebus/track2-preview6-add-sas-token-auth
Sep 10, 2020
Merged
Changes from all commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
e666f57
- Remove public documentation and exports of ServiceBusSharedKeyCrede…
KieranBrantnerMagee ac20634
Merge from upstream master
KieranBrantnerMagee 902f92d
pylint and mypy fixes
KieranBrantnerMagee d1062f6
Add safety net for if signature and key are both provided in connstr …
KieranBrantnerMagee 892b612
remove spurious changelog line, disable SAS token non-se= SAS test pe…
KieranBrantnerMagee e05c349
Merge from upstream master
KieranBrantnerMagee f3b51fb
Merge from upstream master
KieranBrantnerMagee f8d8ad1
Fix async mgmt client conn str parsing order
KieranBrantnerMagee f83bf4c
Fix lint error (extra space)
KieranBrantnerMagee df456b6
Merge branch 'master' into kibrantn/servicebus/track2-preview6-add-sa…
KieranBrantnerMagee 7937c8f
Update sdk/servicebus/azure-servicebus/tests/async_tests/test_sb_clie…
KieranBrantnerMagee 1934db9
remove spurious debugging prints
KieranBrantnerMagee c7ee6f2
Merge branch 'kibrantn/servicebus/track2-preview6-add-sas-token-auth'…
KieranBrantnerMagee 78486e7
Merge from upstream master
KieranBrantnerMagee File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
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.