I'm doing it by choosing my currently log on user before pressing the "deploy" button, (which is a domain admin.). If I try doing it with an "Installer Action" it always asks me for the username and password and also need to press YES multiple times. I've tried so many things that don't ask for my admin account and password, but I still need to say YES when windows asks me if I'm sure I want to run the updater.Ĭurrently I'm running this command in the Deployment Install packages:Įtwork NAS where we have the vaccine\vaccine.exe""
I'd like to know if anyone knows how I can do it correctly. I can do it manually, but it's not worth doing it this way because I have over 80 computers at work.
exe file, but I can't find a way to do it without pressing the "yes" button multiple times. I just don't understand why it is acceptable to change the Principle? Surely it should be fine to let that be set by JAAS and maintained, and just the role changed by 'run as' rather than changing the role (as expected) but also deleting the principle? Does anyone know if there is another way round getting the DAOs not be called by the webclient without using RunAs? I could remove the RunAs though this screws up my security model as in theory my JSF beans could call my dao EJBs directly (which I don't want) Or ideally.Hi everyone, I am trying to update my Symantec Endpoint Protection database with an. but as far as I can see, there's no way of passing in the original principal Surely there's a hole in the spec if this anyone using a Service-DAO ejb pattern can't use caller principle in the DAO? I can't be the first to of hit this type of problem, whereby I need to use 'run as' to change the ROLE in the service so the DAO can't be called directly(by using RolesAllowed). Now you can use to manually set the principal when the dao EJB is delared. Though when I call getUserPrinciple within daoEJB gets a caller principle on ‘anonymous’ instead of the correct principle set by JAAS. serviceEJB then calls methodA of daoEJB with a set to “SERVICE� (to stop the JSF web client being able to call daoEJB directly - with RolesAllowed set on the DAO). Now when serviceEJB calls getUserPrinciple it returns the principle correctly. I have a JSF which calls a serviceEJB which in turn calls a daoEJB.
0 kommentar(er)
