ALLOut Blog


Access Management in JD Edwards (JDE) Security

What does Access Management mean?

Access management is the process of identifying, tracking, controlling and managing authorized or specified user's access to a system, application or any IT instance.

It is a broad concept that encompasses all policies, processes, methodologies and tools to maintain access privileges within an IT environment. It is primarily an information security, IT and data governance process used in granting access to valid users and prohibiting invalid users.

JDE EnterpriseOne and Access Management

Audit History Reporting in JD EnterpriseOne (JDE)

Did you know you can switch on your security logging in the JDE ini file?  (Enter 1).  Once it's turned on the F9312 table will provide audit logging.  But it tracks more than just sign on!  It will also track changes to:

JDE Security Recommendations for UDOs

UDOs are personalized web-based objects that can be created by users to improve their JDE experience and reduce the requirement for developer involvement.

Once a UDO(s) has been approved (shared), security must be created to grant authority to the user(s) that will utilize the UDO(s).

There are a number of stages to setting up effective security over UDOs if they are being utilized.

ALLOut makes this process substantially simpler for you!

JDE Security – Closed vs. Open

Security is a vital component of your JD Edwards environment and needs to be implemented properly to make full use of its benefits. At ALLOut, we are all about ‘Best Practice’ because we genuinely want our customers to have the smoothest ride in setting up and working with security in JDE.  Done correctly, it doesn’t have to be confusing and hard to implement, regardless of whether you implement it before or after go-live.

Mitigating Controls – Should you use them? What controls should you have?

Mitigating Controls in JD Edwards.

Mitigating controls on a risk situation is never as desirable as an effective segregation of duties.  But it is recognised that in some situations, a breach of a security rule may just have to exist (for example if someone is providing temporary cover for another role within their department). 

What sort of mitigating or compensating controls should you consider?