1. Security Administration Guide
  2. Understanding Security Overrides

Understanding Security Overrides

Security overrides operate as exceptions to existing security records. They specify that users are unsecured from an EnterpriseOne object. In other words, security overrides allow users access to a particular object, even if another security record in the system specifies that access is not allowed.

Security overrides enable you to create object security more efficiently, with fewer security records to manage. For example, you might have a scenario that requires securing four out of five versions of an application from a group of users. Instead of creating four security records to prevent users from accessing each of the four versions, you can create two security records to achieve the same result. First, you would create a security override for the application version that you want users to access. This security override would specify that this version is not secured. These are the high level steps to create security overrides in Security Workbench:

  1. Create a security record for the version, making sure that the security options are cleared.

  2. Create a security record that secures users from accessing the application, including all versions of the application. In Security Workbench, you would select the application and then select the Run security option, which secures users from running the application.

As a result, when users try to access the application version, the security override for the version operates as an exception to the second application security record, allowing users access to the version of the application. All other versions of the application are secured.

You can create security overrides for these JD Edwards EnterpriseOne objects:

  • Applications

  • Actions

  • Processing options

  • Tabs

  • Hyper exits

  • External calls

  • Push buttons, links, and images

  • Media objects

Creating security overrides simplifies the process of applying security to various EnterpriseOne items. The following table provides some scenarios in which you could use security overrides to set up your security:

Scenario

Method

Allow a user or group of users access to a single form in an application. These users are otherwise restricted from using the application.

To set up:

  1. Create a security override for the form.

  2. Create a security record to prevent users from accessing the application.

Secure users from using all but one push button on a form in an application. This security shall apply to all versions of the application as well.

To set up:

  1. Create a security override for the push button.

  2. Create a security record to prevent users from using all push buttons on the form.

Allow only one user in a role access to an external application.

To set up:

  1. Create a security override for the user that gives the user access to the external application.

  2. Create a security record that prevents the role from accessing the external application.

Secure users from all action buttons except Add and Copy on a form in a particular version of an application.

To set up:

  1. Create a security override to specify that Add and Copy action buttons are not secured on a form in a particular version of an application.

  2. Create a security record to secure all actions on the form.

Before you can create a security override for an EnterpriseOne object, you must first understand how a standard security record for the object is created in Security Workbench. See the appropriate sections in this chapter for instructions on how to apply security to EnterpriseOne objects such as applications, processing options, tabs, and media objects.