Will elog defer user identification and authorization to the ssl engine of a *local* Apache proxy? I'd like to try elog in a site that requires the service port positively authenticate and identify users via smartcard certificate ID. Per SOP they have Apache+mod_ssl setting SSLUserName=SSL_CLIENT_S_DN_CN which sets both the SSL request object's "user" field and the REMOTE_USER environment var relative to the mod_ssl's session's process group leader. Users auth with Apache's mod_ssl as a single-signon replacement for web apps which have traditional native, internal user accounts/passwords, but those passwords are subsumed by the Apache/smartcard/mod_ssl setup. The web apps define internal accounts matching the users' cert IDs but do not allow any management of the [unused] passwords. Can elog do this? |
Hi Stefan,
Thanks for the great work. We have been using elog for a year as inventory management.
Now we have a long list of attributes in our logbook, some of those we want to keep in database for record, but we don't want to see them because they are not used very often. I tried the "Show Attributes". my conf is like this:
Attributes = Name, SysAdmin, OS, Manufacturer, Model, Serial Number, Description, Main Function, Location, Memory, CPU Speed, Num CPU, Owner, Contact Name, Contact Phone, Contact Email, Bought From, Bought Date, Maintenance, Network Drop, Console Drop
.
.
.
Options OS = SunOs{1}, Linux{2}, Aix
{1} Show Attributes = Name, SysAdmin, OS, Manufacturer, Model, Serial Number, Description
but it seems only effective when adding the new entry. All the attributes will show in logbook. Is there a way to hide some of the attributes? It would be good to let each user to choose what to see what not to see, create their own view. Can you put it on your to-do list or wishlist?
Thanks |
I am trying to add additional information to the subject of new entries:
Subst subject = $subject [INCIDENT $message id]
Subst on reply subject = Re: $subject
Fixed Attributes Reply = Subject
However, the new entry subject looks like:
this is my subject [INCIDENT this is my subject [INCIDENT $message id]
I'm not sure if there's a problem with the substitution or if this is just not allowed (I'm having LISP flashbacks).
By the way, if I use "Subst on reply subject" I get the behavior I would like but the original entry in the thread doesn't contain the appended data:
Subst on reply subject = Re: $subject [INCIDENT $message id]
Any help would be appreciated.
Alex |
Just compiled 1.410 and have run into an issue that *may* have been
introduced in 1.393.
Config file directives such as "Welcome title" could be very long strings.
After compiling 1.410, our "Welcome title" is truncated and, while I haven't
counted the actual chars, I suspect that the truncation happens at 1024
characters. The procedure 'getcfg' has a declared passed paramater "int
vsize".
I haven't looked to see if this effects any other large configuration
strings that are managed by "getcfg" but this procedure is perhaps the most
popular one by far in elog. |