James Monroe
Active Member
We are on JDE E1 9.0, tools 9.1.4.7.
During a data masking project started upon by our IT, we were testing the third party data masking solution and it ran into an issue with the fact that all Oracle DB objects were set to give all privileges to PUBLIC. This is prevent the data masking solution from working.
Opening a ticket with Oracle, they confirmed that prior to 9.2, all database objects are shipped with all privileges assigned to PUBLIC. As of 9.2 this has been changed, but it presents an issue with our 9.0 and data masking.
Oracle/JDE support provided a document 'Oracle Public Shutdown for JD Edwards EnterpriseOne'. This document and the accompanying scripts represent an approach that can be used to move from PUBLIC to where you are giving specific privileges. And the document does say that this document describes an 'approach' that can be used and implies that you may need to review it for your particular environment.
Has anyone had to do this type of thing, moving away from the delivered PUBLIC security. Any experiences to share as to difficulty or things to look for?
I am a long time JDE developer, not a CNC consultant but can build/deploy packages. That is about the extent of my CNC knowledge. Does this solution of moving away from PUBLIC oracle security setup seem pretty straighforward? or is this something that you might want a more experienced CNC person on consultant.
View attachment Oracle Public Shutdown for JDEdwards EnterpriseOne.pdfView attachment Oracle Public Shutdown for JDEdwards EnterpriseOne.pdf
During a data masking project started upon by our IT, we were testing the third party data masking solution and it ran into an issue with the fact that all Oracle DB objects were set to give all privileges to PUBLIC. This is prevent the data masking solution from working.
Opening a ticket with Oracle, they confirmed that prior to 9.2, all database objects are shipped with all privileges assigned to PUBLIC. As of 9.2 this has been changed, but it presents an issue with our 9.0 and data masking.
Oracle/JDE support provided a document 'Oracle Public Shutdown for JD Edwards EnterpriseOne'. This document and the accompanying scripts represent an approach that can be used to move from PUBLIC to where you are giving specific privileges. And the document does say that this document describes an 'approach' that can be used and implies that you may need to review it for your particular environment.
Has anyone had to do this type of thing, moving away from the delivered PUBLIC security. Any experiences to share as to difficulty or things to look for?
I am a long time JDE developer, not a CNC consultant but can build/deploy packages. That is about the extent of my CNC knowledge. Does this solution of moving away from PUBLIC oracle security setup seem pretty straighforward? or is this something that you might want a more experienced CNC person on consultant.
View attachment Oracle Public Shutdown for JDEdwards EnterpriseOne.pdfView attachment Oracle Public Shutdown for JDEdwards EnterpriseOne.pdf