digiofficerobin

Results 5 comments of digiofficerobin

[Bug] project update to net8.0, after the jwt "System.IdentityModel.Tokens.Jwt 7.0.3" throw an error ： “IDX12723: Unable to decode the payload \u0027[PII of type \u0027System.String\u0027 is hidden. For more details, see https://aka.ms/IdentityModel/PII.]\u0027 as Base64Url encoded string.”

I have a similar message: IDX12723: Unable to decode the payload '[PII of type 'System.String' is hidden. For more details, see https://aka.ms/IdentityModel/PII.]' as Base64Url encoded string. In the debugger I...

[Bug] project update to net8.0, after the jwt "System.IdentityModel.Tokens.Jwt 7.0.3" throw an error ： “IDX12723: Unable to decode the payload \u0027[PII of type \u0027System.String\u0027 is hidden. For more details, see https://aka.ms/IdentityModel/PII.]\u0027 as Base64Url encoded string.”

> @digiofficerobin > > JTI per the RFC is a string. > > See [here](https://www.rfc-editor.org/rfc/rfc7519.html#section-4.1.7) > > Please open a separate issue specifically around ServiceStack compatibility, Oke, thanks, I'll contact...

[Bug] project update to net8.0, after the jwt "System.IdentityModel.Tokens.Jwt 7.0.3" throw an error ： “IDX12723: Unable to decode the payload \u0027[PII of type \u0027System.String\u0027 is hidden. For more details, see https://aka.ms/IdentityModel/PII.]\u0027 as Base64Url encoded string.”

> @digiofficerobin did you hear from ServiceStack? I would like to know if this issue of JTI as a Json.Number is common. > > I marked it as a regression...

[Bug] project update to net8.0, after the jwt "System.IdentityModel.Tokens.Jwt 7.0.3" throw an error ： “IDX12723: Unable to decode the payload \u0027[PII of type \u0027System.String\u0027 is hidden. For more details, see https://aka.ms/IdentityModel/PII.]\u0027 as Base64Url encoded string.”

In the past, a Number wasn't an issue. Which is a breaking change. That may not cause a problem if this is communicated well in the release notes of the...

[BUG] Inaccurate error message "The specified container does not exist" when uploading data with empty blob name using BlobClient.

I had the same issue today. The error "The specified container does not exist." still remains confusing. The container is available, but my filename was an empty string.