JD Edwards 3rd party security tools

The security mechanism both for World and EnterpriseOne is very complex. End-users need to create security restrictions in the applications to authorize the right users for the right content, to ensure data protection policies are enforced etc. These requirements generate a need for making security easier to apply and administer. There are 3rd party tools available that address this need.

We see that more and more JD Edwards end-users are using such tools. The issue with this is that licensing is not among the purposes for which these tools are built. In fact, the security restrictions they add are often insufficient to ensure consumption of the right amount of licenses. JD Edwards administrators would therefore need to add additional security rules directly into EnterpriseOne or World, just for licensing purposes. This raises two questions:

  1. Do administrators know how to do that if they have only been trained to add security using the 3rd party tools?
  2. Can the security restrictions they add directly conflict with those added from the 3rd party security tool?

Since the setup of  the security tools as well as of World or EnterpriseOne is quite complex we see many implications on licensing. Whilst it is impossible to give a one-size-fits-all advice in this matter, the message is that these situations need to be handled carefully and organizations should not forget about licensing when they configure their security rules.

This was our last article about licensing JD Edwards. More information can also be found in our white paper “JD Edwards – License Compliance Risks”. Our new white paper format is mobile friendly, so you can easily read it on your tablet or mobile phone.

B-lay helps organizations effectively use and manage their software assets with practical solutions and services. We love helping you avoid costs, so contact us for support on your JD Edwards license issues!

This article was published on 02-08-2016