E1: SEC: Overview of Application Security Defined Within The Security Workbench Application (P00950). (Doc ID 1367482.1)

Last updated on APRIL 30, 2024

Applies to:

JD Edwards EnterpriseOne Tools - Version 8.98 and later
Information in this document applies to any platform.

Purpose

This document provides an overview of setting up Application Security defined within the Security Workbench application (P00950).

Overview

Application Security is defined within the Security Workbench application (P00950). Application Security enables you to restrict or allow users to access specific applications, versions of applications or forms within an application. This includes UBEs (Universal Batch Engines) such as Rxxxxx.

Application Security can be defined at multiple different levels.

You can define Application security at the Application level. This will secure all versions and forms associated with that application.
You can define security at the Version level for an application. This will allow you to define security for specific versions of an application while leaving other versions available to the user.
You can define security at the Form level allowing you to secure access to a single form in an application or application version.

In addition to defining Application security at the application level, you can also define Application Security for *ALL objects, securing the user from all objects by default within the EnterpriseOne system. When using this method of security, Application Security must then be setup allowing access to the specific applications the user requires to perform their job functions.

You can set up Application security at three levels:

User
Role
*PUBLIC

EnterpriseOne first looks for Application Security at the User level, then at the Role level, and then at the *PUBLIC level. If you set any of the security at a higher level, such as at the user level, the software ignores lower-level security settings, such as the Role or *PUBLIC levels.

Application Security can also be applied on different roles and then the roles combined for the user when the user signs on to EnterpriseOne as *ALL. The security check starts at the role with the highest sequence number and then checks to see if there is any application security defined. Once it completes the first role, it checks the next role. If it does not find any conflicts, then it will add the security for each role. If any conflicts exist within the Application Security settings, then only the Application security defined for the role with the higher sequence number will be applied. A conflict would be application security defined for the same application on two different roles. See Doc ID 1087848.1 for additional details on roles and security.

Application security defined for an application or version will prevent this item from displaying as an available task for a secured user within the EnterpriseOne menus. If a user attempts to launch an application, from Fast Path or the versions list, where Application Security has been defined preventing access, the user will receive an error message such as "You are Not Authorized to Execute this Application", "You are Not Authorized to Execute this Task" or "You are Not Authorized to Run this Application".

For additional information on Application Security, refer to the JD Edwards EnterpriseOne Tools Security Administration Guide available on the Oracle Technology Network. In addition, to answers on frequently asked questions regarding Application Security, refer to Doc ID 1212684.1.

Following are the topics discussed in this document: