Interfaced with SSO, posted by Patricia Mendez Lorenzo on Fri Mar 22 09:53:39 2019
|
Dear Supporters,
I am evaluating the elog software as lobgook for high energy pgysics and I was just wondering the interface with SSO from the login point of view. Once euthenticated with SSO, can this authentication be also recognized by elog?
Thank you so much
Best Regards,
PAtricia |
elog client through proxy, posted by gibelin julien on Mon Mar 25 12:31:34 2019
|
Dear users,
we started an elog serveur (using ssl) and open to the world which is working fine.
However I am trying to access it via the command line client, from a computer that uses a proxy to connect to internet.
The environnment variable are set :
declare -x ftp_proxy="ftp://myproxy:3128/"
declare -x http_proxy="http://myproxy:3128/"
declare -x https_proxy="https://myproxy:3128/"
declare -x socks_proxy="socks://myproxy:3128/"
but when I try to connect
elog -h myelog -p 443 -l lognote -s 1 -u username passwd -w last
I have the following message :
Cannot connect to host myelog, port 44
How should I proceed ?
Best regards
JG
:
|
Hiding Logbook tabs, posted by Alan Grant on Thu Mar 28 21:55:14 2019
|
I know you can restrict access to logbooks on per user basis but can anyone tell me if it is possible to HIDE certain logbook tabs/groups on per user basis (ie, so they would just see logbooks they are authorized to see)? |
Pinned entry, posted by Giuseppe Cucinotta on Thu Apr 18 12:29:05 2019
|
Hi everybody,
sorry if this question has already been posed (I did a quick search but I didn't found anything): elog sorts entry by ID, I wonder if it is possible to pin an entry in order to be always on top of the page independently on its ID.
Thanks
Giuseppe |
exclude access to a number of users in one logbook, posted by Nikolas Patronis on Wed Apr 24 09:15:26 2019
|
How can I exclude the access of a number of users in one (out of two) logbooks running in the same server and URL? |
Last default = <n>, posted by Alan Grant on Mon Apr 29 02:41:15 2019
|
According to the doc on the setting "Last default = <n>" it is intended to restrict Quick Filter searches to the last (n) days of entries, however when I add "Last default = 28" to config it still returns entries far older then 28 days when using the filter search. Am I misunderstanding, or implementing it wrong? We must restrict searches through QF to reduce load.
A couple other side questions which are related:
The doc on this setting says: "Last default = <n>
Some logbooks are very big ans searching through all entries with quick filter can be time consuming. This option sets a default value for the Date quick filter, so that by default only the <n> days are displayed." ...... I'm assuming that by saying "only the <n> days are displayed" that it has actually only searched <n> days ................ vs seaching ALL the logbooks but only displaying <n> days. Please confirm.
Also, why wouldn't the "28" days spec display in the Select Period box beside the Quick Filters? Otherwise it appears to me to be a separate and conflicting item. Best regards! |
How to sort on any field?, posted by John on Tue Apr 30 05:52:44 2019
|
Hi, I was wondering if this is possible. I've tried to sort on anything other than the first few fields and although the screen refreshes like it is 'doing something', it does NOT sort. Sometimes it will take me to the last page of my data, but still no sorting. I use Debian Linux verson of Elog. There have been no other issues. I need to figure out how to do this without parsing it to another program first. Thanks again for this wonderful program :)
John |
Execute attribute, posted by Alan Grant on Fri May 10 04:34:36 2019
|
Apart from an inline shell command that can be run with the Execute attribute, is it possible to run an external script file? I would like to run a Powershell script with the Elog attribute data parameters passed to it upon Submit New entry. |