Sorry, you cannot just use ALLOW = *. The HTCondor security layer would not understand it. What you have here
ALLOW_READ = *Â
ALLOW_DAEMON = $(CONDOR_HOST), submit*.
wisc.edu, worker*.
wisc.edu
ALLOW_NEGOTIATOR = $(CONDOR_HOST)Â
ALLOW_ADMINISTRATOR = $(CONDOR_HOST)Â
I probably the minimum number of allow statements that you can get away with for the central manager.Â
The AP (schedd), will also need
ALLOW_WRITE = ??
where ?? is a pattern that matches what users are allowed to submit jobs. ÂIf you trust your firewalls
then ALLOW_WRITE = * should be fine here. Â
Otherwise it should be a pattern that matches valid usernames like.ÂÂ
ALLOW_WRITE = *@$(UID_DOMAIN)
-tj
Subject:Â[HTCondor-users] ALLOW_ question and upgrade
Â
We recently upgraded to 10.x series of Condor. We want to secure it but also add additionalÂfunctionalityÂfor users.Â
My question is,Â
ALLOW_READ = *Â
ALLOW_DAEMON = $(CONDOR_HOST), submit*.
wisc.edu, worker*.
wisc.eduÂALLOW_NEGOTIATOR
= $(CONDOR_HOST)Â
ALLOW_ADMINISTRATOR = $(CONDOR_HOST)Â
Do I need all these parameters? Can I just say ALLOW = * ?Â
Second,Â
I want remote submissions. So, from a host which has condor binaries, I would like to submit jobs like this. condor_submit -sched hostK1. Where hostK1 has schedd running.
--
--- Get your facts first, then you can distort them as you please.--