You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The app is in production, and I have upgraded to a new version of MSAL
Issue description and reproduction steps
When the broker additional fields and telemetry fields were added the tojson and fromjson methods were not updated to include serializing the additional fields.
Relevant code snippets
MSALExceptionpublicstringToJsonString()publicstaticMsalExceptionFromJsonString(stringjson)
are missing
public const string BrokerErrorContext ="BrokerErrorContext";publicconststringBrokerErrorTag="BrokerErrorTag";publicconststringBrokerErrorStatus="BrokerErrorStatus";publicconststringBrokerErrorCode="BrokerErrorCode";publicconststringBrokerTelemetry="BrokerTelemetry";
Expected behavior
Those fields should also be serialized.
Identity provider
Microsoft Entra ID (Work and School accounts and Personal Microsoft accounts)
Regression
No response
Solution and workarounds
No response
The text was updated successfully, but these errors were encountered:
pmaytak
changed the title
[Bug] ToJson does not serialize all fields of MSAL exception leading to data loss when deserialized
[Bug] ToJsonString does not serialize all fields of MSAL exception leading to data loss when deserialized
Oct 12, 2023
Library version used
4.54
.NET version
.net framework 4.7 .net 6, net 8
Scenario
PublicClient - desktop app
Is this a new or an existing app?
The app is in production, and I have upgraded to a new version of MSAL
Issue description and reproduction steps
When the broker additional fields and telemetry fields were added the tojson and fromjson methods were not updated to include serializing the additional fields.
Relevant code snippets
Expected behavior
Those fields should also be serialized.
Identity provider
Microsoft Entra ID (Work and School accounts and Personal Microsoft accounts)
Regression
No response
Solution and workarounds
No response
The text was updated successfully, but these errors were encountered: