Hello,
Currently, XAF Security doesn't support shared parts when working with Domain Components and it is difficult to improve it shortly. We need some time to investigate this situation, find a solution and implement it.
This is why I have duplicated this issue to the following ticket: Security - Support domain components in the new security system (Client-Side UI and Integrated modes). This issue will be fixed when we finish that ticket.
Please track it to be notified when its status is changed. Thanks for your patience.
Thanks,
Dan
We have closed this ticket because another page addresses its subject:
Security - Support domain components in the new security system (Client-Side UI and Integrated modes)Security.DC - The IsGranted method always returns 'false' for entities that were registered with the help of the XafTypesInfo.Instance.RegisterSharedPart method
Answers approved by DevExpress Support
created 13 years ago
(modified 13 years ago)
Comments
(2)
We cannot create an explicit m-m in DC. Now i discover we cannot even save a simple DC-based BO that consists of a shared component. This is the very heart of DC. How was this missed? To repeat: this is the very heart of DC. This was discovered at least 6 months ago. Help us understand why this is not corrected for pre12.1 bits. Baffled and very frustrated.
We elaborated more on this at How to implement SecuritySystem on Domain Components?.
In the meantime, it is possible to use the "old" security system interfaces with DC, as it is demonstrated in our XCRM demo.
Other Answers
created 13 years ago
(modified 13 years ago)
I posted a solution for this at: Q363027
I worked for me, I hope it works for you.