The process of setting up user and role profiles in EnterpriseOne for sign-in security (authentication) and authorization security.
The process of verifying that users signing into EnterpriseOne are valid EnterpriseOne users.
The process of granting or denying users access to EnterpriseOne applications, features, data, and data sources. In EnterpriseOne, most authorization security is applied at the object level through the Security Workbench.
The process of transforming information into code so that it cannot be read by a third party system. EnterpriseOne encrypts user passwords stored in the database.
Customizing a field so that specified characters are embedded in place of sensitive data that appears in applications. This prevents sensitive data from being displayed to unauthorized users.
In EnterpriseOne, Address Book data security enables you to restrict users from viewing Address Book information that is determined as private, personal data.
Security that determines the actions that developers can perform when customizing or developing EnterpriseOne applications in Object Management Workbench (OMW). Actions can include checking out and checking in objects, promoting objects, transferring objects, removing objects, and so forth.
A type of authorization security that enables you to secure specific objects within JD Edwards EnterpriseOne such as applications, forms, and various other EnterpriseOne features. Object-level security provides flexibility with applying security and a higher level of security integrity.
A special ID within EnterpriseOne that automatically includes all users within it. This option controls security for all users who are designated by ID type *PUBLIC in the User or Role field.
Web-only application forms that enable users to view multiple, interrelated views of data, grids, and tab pages on one form and to pass logic between them.
EnterpriseOne service level logic and interface. A classification of a published business service indicating the intention to be exposed to external (non-EnterpriseOne) systems.
A security model that assumes that a user does not have permission to execute an object unless there is a specific record indicating such permissions.
A security protocol that provides communication privacy. SSL enables client and server applications to communicate in a way that is designed to prevent eavesdropping, tampering, and message forgery.
Security records that operate as exceptions to existing security records. Security overrides 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.
An application that enables you to secure JD Edwards EnterpriseOne objects, such as applications, forms, rows, tabs, and so on. It stores all objects security records in the F00950 table.
The process of converting an object or data into a format for storage or transmission across a network connection link with the ability to reconstruct the original data or objects when needed.
A subform is a control designed for use on a power form or another subform. Power forms can contain several subforms, so a single power form with multiple subforms enables users to see multiple data views.