Skip to content
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

CBS Auth errors when trying to use a SAS token without a se= stanza #170

Closed
KieranBrantnerMagee opened this issue Sep 8, 2020 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@KieranBrantnerMagee
Copy link
Member

  • UAMQP Package Version:
    latest
  • Operating System:
    all
  • Python Version:
    all

Describe the bug
Utilize a SAS token lacking a &se= stanza. Observe the following error:
E uamqp.errors.TokenAuthFailure: CBS Token authentication failed.
E Status code: 500
E Description: The service was unable to process the request; please retry the operation. For more information on exception types and proper exception handling, please refer to http://go.microsoft.com/fwlink/?LinkId=761101

To Reproduce
Steps to reproduce the behavior:

  1. Generate a SAS token as observed in this Service Bus test
  2. Try to authenticate/send/do any operation

Expected behavior
Should succeed to authenticate.

@yunhaoling
Copy link
Contributor

yunhaoling commented Sep 22, 2020

Closing this issue now, the summary is as bellow:

Based on

We conclude that "se=" is required scope for a sas token and the expiry information is included in the token string to be hashed.

@yunhaoling
Copy link
Contributor

new action item for you @KieranBrantnerMagee: we may need to remove the optionality in SB.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants