Wpf InvalidCastException on UnauthenticatedPrincipal upgrading to 5.4.0

[JacoJordaan]

Upgrading from 5.3 to 5.4 I get the following exception on my DataPortal call from the WPF application:

Csla.Server.DataPortalException: DataPortal.Fetch failed on the server
   at Csla.AspNetCore.ApplicationContextManager.SetUser(IPrincipal principal)
   at Csla.ApplicationContext.set_User(IPrincipal value)
   at Csla.Server.DataPortal.SetContext(DataPortalContext context)
   at Csla.Server.DataPortal.Fetch(Type objectType, Object criteria, DataPortalContext context, Boolean isSync)
   at Csla.Server.DataPortal.NewDataPortalException(String message, Exception innerException, Object businessObject)
   at Csla.Server.DataPortal.Fetch(Type objectType, Object criteria, DataPortalContext context, Boolean isSync)
   at Csla.Server.Hosts.HttpPortal.Fetch(CriteriaRequest request)
   at Csla.Server.Hosts.HttpPortalController.CallPortal(String operation, Object request)
   at Csla.Server.Hosts.HttpPortalController.InvokePortal(String operation, Stream requestStream, Stream responseStream)
System.InvalidCastException: Unable to cast object of type 'Csla.Security.UnauthenticatedPrincipal' to type 'System.Security.Claims.ClaimsPrincipal'.
   at Csla.AspNetCore.ApplicationContextManager.SetUser(IPrincipal principal)
   at Csla.ApplicationContext.set_User(IPrincipal value)
   at Csla.Server.DataPortal.SetContext(DataPortalContext context)
   at Csla.Server.DataPortal.Fetch(Type objectType, Object criteria, DataPortalContext context, Boolean isSync)

Any ideas how to correct his error?

The Blazor server client is working fine. Only the WPF client connecting to the remote data portal throwing this error.

[rockfordlhotka]

aspnetcore only supports ClaimsPrincipal and ClaimsIdentity, so you can't use custom IPrincipal or IIdentity types in that environment.

In fact, in CSLA 6 I'm removing all the types that help you create custom principal/identity classes, because that's just a dead end apparently.

[JacoJordaan]

I have made the changes previously to my business objects to use only ClaimsPrincipal and ClaimsIdentity. Blazor server UI is working fine with same business objects.
Should the Blazor server UI not also giving me the same error?

[rockfordlhotka]

I'm not 100% sure Blazor has the same limitation, though I think it does.