DC - Provide support for Domain Components in the RemoteSecuredDataServer/WcfSecuredDataServer classes

BTW, to temporarily make it work in the middle-tier scenario,

1. you need to ensure that both client and server applications use the same version of generated domain components. To do this, copy the generated DcAssembly.dll file from the client application (it is generated in the Release mode near the executable file by default) into the Bin folder of your server application and also override the GetXXXPath methods of the ServerApplication class as follows:

C#
public class ConsoleApplicationServerServerApplication : ServerApplication {  
        private string applicationFolder;  
        public ConsoleApplicationServerServerApplication() {  
            applicationFolder = PathHelper.GetApplicationFolder();  

            // Change the ServerApplication.ApplicationName property value. It should be the same as your client application name.  
            this.ApplicationName = "SecuritySystemExample";  

            // Add your client application's modules to the ServerApplication.Modules collection here.  
            this.Modules.Add(new SystemWindowsFormsModule());  
            this.Modules.Add(new SystemAspNetModule());  
            this.Modules.Add(new SecuritySystemExampleModule());  
            this.Modules.Add(new SecurityModule());  
        }  
        protected override void OnDatabaseVersionMismatch(DevExpress.ExpressApp.DatabaseVersionMismatchEventArgs args) {  
            args.Updater.Update();  
            args.Handled = true;  
        }  
        protected override void CreateDefaultObjectSpaceProvider(CreateCustomObjectSpaceProviderEventArgs args) {  
            args.ObjectSpaceProvider = new XPObjectSpaceProvider(args.ConnectionString, args.Connection);  
        }  

        protected override string GetDcAssemblyFilePath() {  
            return Path.Combine(applicationFolder, DcAssemblyFileName);  
        }  
        protected override string GetModelAssemblyFilePath() {  
            return Path.Combine(applicationFolder, ModelAssemblyFileName);  
        }  
        protected override string GetModulesVersionInfoFilePath() {  
            return Path.Combine(applicationFolder, ModulesVersionInfoFileName);  
        }  
    }  

So, this suggestion is mainly about improving usability in this scenario and also ensuring that there are no other technical issues so far.
OR
2) You can use a solution posted by Daniel Großer in Security - Support domain components in the new security system (Client-Side UI and Integrated modes).

thx Dennis,
is there a way to figure out the path of the DcAssembly?

The DcAssembly.dll file is generated in the Release mode near the executable file by default.

Is this going to make it in the 13.1 release? This really should have been in 12.2 along with the UI and Integrated modes but I sure hope it makes it into 13.1.