This example illustrates how to create custom security objects, such as permissions, roles and users. We will implement a permission that allows administrators to secure the exporting functionality in an XAF application. The complete description is available in the How to: Implement Custom Permission, Role and User Objects topic.
Question Comments
Added By: Leong Vai Long at: 4/30/2014 3:24:41 AM
Hi DX,
How can I rename these 7 SecuritySystem* tables in database?
How to change their Oid to Int64 instead of GUID? My other BOs are inheriting from XPObject.
Thanks.
You can implement security system classes from scratch and use a key propety of a requred type instead of inheriting built-in classes: How to: Implement a Custom Security System User Based on an Existing Business ClassAdded By: Amin Baig at: 2/28/2016 9:04:22 AM Hi,
How can this example be used to create a role which can create new users. I know the Administrator can create users, but then Administrator role has complete visibility of everything.
In my scenario, the Administrator role is only for the system owner that is myself, and my system is a cloud based multi-tenant system. So I have to create a role which can create new users, but does not have full control on everything.
Regards. Added By: Konstantin B (DevExpress) at: 2/28/2016 11:29:35 PM Hi Amin,
In your scenario, you can create a security role and grant it write permissions for a user type.
Added By: Amin Baig at: 2/29/2016 2:21:24 AM Hi Konstantin,Can you guide me to an example/demo on how this can be achieved?
Regards. Added By: Konstantin B (DevExpress) at: 2/29/2016 2:30:15 AM
I am afraid we have no separate example for this scenario, but actually it does not differ from granting permissions for any other business object type. A security system user is a regular business object and there is no need to grant access to it in some special way. In the context of the current example, the security system user type is Employee.