Apply to your VIGILENS requests the security of your JDE user
The optional JDEUtil module allows you to improve the integration of Vigilens with JDE EnterpriseOne, by dynamically retrieving in Vigilens, at runtime from JDE/E1 :
Now, the user CO_ALL connects to JDE and clicks on a Vigilens link:
The user does not reconnect in VIGILENS, nor does he use a generic user
The user CO_ALL has no restriction in JDE, the execution of the query displays the result for all the companies.
The user CO_00070 connects to JDE and clicks on a Vigilens link:
The user does not reconnect in VIGILENS, nor does he use a generic user
The user CO_00070 only has access to the company 00070, VIGILENS adds this restriction automatically when the request is executed,
JDEUTIL is a JD Edwards application specifically developed by VIGILENS (P59VLVIG) to apply the line security of the connected JDE user to queries executed from JD Edwards web.
The URL used is hidden and ephemeral
The identifier passed to VIGILENS is a unique key generated by JDEUTIL (P59VLVIG). The identifier is therefore anonymous
VIGILENS will then delete the record containing the ID. Even if we manage to reuse the hidden URL, it will no longer be valid
THE SECURITY IS THUS MAXIMUM
JDEUtil consists of several JDE/E1 objects, including:
These objects are delivered as a .par file, which must be restored in JDE by OMW. The objects must be promoted, packaged and deployed in all environments where JDEUtil is to run. The specific table must be generated in the different data sources.
To ensure the correct behaviour of the application when launching the connection chain, it is necessary to set security to prevent the Encoding of the P59VLVIG application.
There are 2 possibilities to use JDEUTIL:
http://adresse_de_JDE/jde/ShortcutLauncher?OID=P59VLVIG_W59VLVIGA_Version_du_P59VLVIG&FormDSTmpl=|1|2|3|4|5|6|7|&FormDSData=|option_de_traitement_1| option_de_traitement_2| option_de_traitement_3 | option_de_traitement_4| option_de_traitement_5| option_de_traitement_6| option_de_traitement_7|