Open bleze opened 2 years ago
What is the error message in the exception?
Can you share an example of your SAS token, with the sensitive information redacted (the part after sig=
)?
Also, since this SDK has been deprecated, we won't fix it even if this was a bug. I suggest you try our Track2 SDK.
Hi Jimming, thanks for the reply!
The exception message is verbose copied to topic of issue.
Here is example of token; https://sgldocumentsdev.blob.core.windows.net/?sv=2020-08-04&ss=bfqt&srt=sco&sp=rwdlacupitfx&se=2022-12-10T18:10:04Z&st=2021-12-10T10:10:04Z&spr=https&sig=
Since the token works fine in Storage Explorer, and I simply cannot see anything wrong with my code, I came here for help.
Working with Microsoft technology is job security. Constantly having to rewrite code due to deprecation. I really hope there is something wrong in my code so I can get this token working, because I'm pressed for time and really do not want to rewrite all this :)
Hi @bleze , can you double check in your code snippet, leSASToken->text().toStdWString()
only returns SAS token excluding schema, domain and path. i.e.
?sv=2020-08-04&ss=bfqt&srt=sco&sp=rwdlacupitfx&se=2022-12-10T18:10:04Z&st=2021-12-10T10:10:04Z&spr=https&sig=XXX
is the SAS token.
Hi Jimming, you're a life saver! I'm pretty sure other tokens with full url has worked with this code, but they weren't for a container. I will have to dig into this, but right now I'm happy. I will add code to split url using regex to make UI more user friendly. Thanks again!
Hi I have working code which works for normal auth and SAS, but not when SAS is for a container. The same SAS Token works fine in Storage Explorer, but not through SDK (7.5.0), where I get the error in topic.
Any ideas what might be wrong? Hopefully in my code and not the SDK :) Thanks