How does eyko interpret, ingest, and enforce JD Edwards security?
This presentation explains how JD Edwards (JDE) security is structured, how it should be configured, and how eyko ingests and applies those same security rules to JDE-sourced data. It outlines the full end-to-end flow, from defining users and roles in JDE to enforcing company-level data access in eyko through Smart Security.
Key points covered:
-
Core JDE Security Tables
F0092 (users and roles), F00926 (role metadata), F95921 (role relationships), and F00950 (security rules such as application or row security).
-
How Security Is Properly Established in JDE
Creating roles, defining users, generating role descriptions, assigning roles, and creating security rules such as company restrictions.
-
How eyko Ingests JDE Security
eyko imports the four JDE security tables, builds an internal security graph of users, roles, and rules, and maps JDE roles to eyko principals.
-
How eyko Applies JDE Security at Runtime
Smart Security evaluates a user’s JDE roles, retrieves active security rules, and applies row-level filters so users only see the companies and data permitted in JDE.
-
End-to-End Security Flow
A unified view showing how JDE establishes security and how eyko enforces the same restrictions on JDE-sourced datasets.