|
When submitting entries via the elog client, I find that I can set arbitrary values for attributes that are supposedly "preset" and "locked".
As an example, I have in my elogd.cfg file:
[global]
...
Group Operations = Accelerator
Top group ATLAS = Operations
...
[global ATLAS]
Attributes = Experiment, Author, Author Email, Category, Subject
Required Attributes = Category, Subject
Options Category = Routine entry, Shift summary, Problem, Fix, Question, Info, Other
Extendable Options = Category
Preset Experiment =
Preset Author = $long_name
Preset Author Email = $user_email
Locked Attributes = Experiment, Author, Author Email
...
[Accelerator]
Attributes = Author, Author Email, Category, Subject
Options Category = Routine entry, Shift summary, Problem, Fix, Question, Info, Other
...
This works as intended with a web client (firefox). The Author and Author Email attributes are preset and unchangeable.
However, if I use the elog client, as in:
elog -v -h my.apache-proxy.server -d elog -l Accelerator -p 443 -s -u johndoe xxxxx -a Category=LN -a Subject=Test -a Author=IDoNotExist -n 1 -m entry.txt
(johndoe is an existing user)
The entry is created with "IDoNotExist" as the Author name, instead of the correct name for the user johndoe,
and the Author Email attribute is blank.
Is there a way to enforce preset and locked attributes in the elogd server? (As a client could connect
with any arbitrary software, not just elog.)
|