I donβt know much about OAS ... but I would suggest that files unpacked from a war file will belong to and be accessible to the user, how OAS works. It is not right? Can you explain a little more about what is actually happening or why is this a problem?
Following your additional comments below ...
It looks like your security model is simply not quite right: you are linking OAS and its data to the dba group, but some dependencies of OAS (and its data) are not in this group. I have a few suggestions:
- Create a new group for OAS and its dependencies and evaluate which users in the dba group should also be in this group. If necessary, save the OAS user in the dba group.
- Deploy the war file with a script that waits for the deployment to complete and changes the permissions for you.
- Fix your dependencies. Sounds such as some of the classes in a war file should rather be deployed elsewhere β outside the application context β and are listed there. They can then have a new, more suitable group to which you add the batch process user and OAS user.
source share