Develop > Persistence layer > Understand access control
Modify access control on existing WebSphere Commerce resources
This section guides you through modifying access control on existing WebSphere Commerce resources. In particular, the following scenarios are reviewed:
- Add a new relationship to an existing WebSphere Commerce entity bean
WebSphere Commerce entity beans that implement the Protectable interface are already protected under access control. The terms of the access control requirements are determined by the way that the bean is used in the out-of-the-box features and functions of WebSphere Commerce. You may encounter situations in which add additional relationships to access control for such beans. For example, if you use an existing bean in some of the customized code, or if you modify an existing WebSphere Commerce public entity bean, you may need to add additional relationships to the bean.
- Add access control to an existing WebSphere Commerce entity bean that is not already protected
If you are using an existing WebSphere Commerce entity bean and the application requires that the bean be protected by access control, you can add this protection.
- Access control implications when a controller command is extended
According to the WebSphere Commerce programming model, you can create the own implementations of existing controller commands. In this case, you create a new implementation class and then associate the new implementation class to the existing interface by updating the command registry.
Related concepts
Related tasks
Create an access control policy
Related reference