Allow password change ???, posted by Hal Proctor on Fri Apr 10 17:41:25 2009
|
How do you allow users to change password for a given logbook when the user keeps getting prompted for admin password to enter the change password feature?
I have Allow password change = 1 set global and at each logbook hoping that would work.
It allows them to change the password when and only when the user gets past the admin login when clicking CONFIG.
help
|
Re: Allow password change ???, posted by Hal Proctor on Fri Apr 10 19:32:33 2009
|
| Hal Proctor wrote: |
|
How do you allow users to change password for a given logbook when the user keeps getting prompted for admin password to enter the change password feature?
I have Allow password change = 1 set global and at each logbook hoping that would work.
It allows them to change the password when and only when the user gets past the admin login when clicking CONFIG.
help
|
Thats what we get for having two people working on the install and configuration. LOL
When first creating and setting up the configs, we had Admin Password = xxxxx entered in each logbook config. Once we created a password list we no longer needed that entry.
This was why each user who had login credentials was being asked to provide the admin password when trying to change their password.  |
|
Re: export the elog data, posted by Hal Proctor on Mon Apr 13 17:35:40 2009
|
| Stefan Ritt wrote: |
|
| urian bardulla wrote: |
|
Hi guys,
Is there any simple way to export the ELOG data in a more readable way, except copying the .log files????
Thank You in advance,
Urian.
|
Click on Find, then select Export to: ..., then click Search. I know it's a bit hidden, but this way one can restrict the subset of entries to be exported.
|
but that method does not export all the data, only the subject lines and category etc.
it does not export the body of the threads. |
|
Re: Allow password change RESOLVED???, posted by Hal Proctor on Tue Apr 14 15:18:11 2009
|
| Stefan Ritt wrote: |
|
| Hal Proctor wrote: |
|
| Hal Proctor wrote: |
|
How do you allow users to change password for a given logbook when the user keeps getting prompted for admin password to enter the change password feature?
I have Allow password change = 1 set global and at each logbook hoping that would work.
It allows them to change the password when and only when the user gets past the admin login when clicking CONFIG.
help
|
Thats what we get for having two people working on the install and configuration. LOL
When first creating and setting up the configs, we had Admin Password = xxxxx entered in each logbook config. Once we created a password list we no longer needed that entry.
This was why each user who had login credentials was being asked to provide the admin password when trying to change their password.
|
I didn't get your point completely, so is this issue now resolved?
|
Yes we had listed within each individual logbook config "Admin Password = xxxx". this was causing the admin login prompt when users wanted to change their own passwords. The "Admin Password =xxxxx" cannot reside on each logbook config when you use a password list and allow users to change their passwords. |
|
Multi Logook Login, posted by Hal Proctor on Tue Apr 14 15:26:14 2009
|
We have two logbooks, each with a different list of users.
The logbooks are open to all network users for read only.
A user with Write permisions logs into his designated logbook.
He then decides to view the other logbook, the one he does not have write permissions to by clicking on the tab to the other logbook.
He is immediately logged out of the logbook he has write permissions to.
He did not close his browser session, only clicked on the other logbook tab.
Is there Any way to keep that person logged into the logbook he has rights to without having the "keep me logged in Checkbox"?
Just like this site has Forum, Config Examples, etc.
Once you select another tab they are logged out of their logbook they just logged in to.
|
|
Re: Access Control, posted by Hal Proctor on Tue Apr 14 20:00:08 2009
|
| Grant Jeffcote wrote: |
| Grant Jeffcote wrote: |
| Yoshio Imai wrote: |
| Grant Jeffcote wrote: | | At present we can give others a full view by adding them to the 'Users' list for each individual logbook, this unfortunately also gives them 'write' access. |
I think the solution to your problem would be to use Deny statements in the configuration sections for the logbooks.
Assume user1, user2 and user3 are in the "owners'" group of logbook1, and user4 and user5 only have "privileged read" access. Then a configuration as follows might help:
Login user = user1, user2, user3, user4, user5
Deny New = user4, user5
Deny Reply = user4, user5
Deny Duplicate = user4, user5
Deny Edit = user4, user5
Deny Delete = user4, user5
Deny Select = user4, user5
Deny CSV Import = user4, user5
This should give them the same read permissions as the logbook owners but should deny any writing operations. I recognize that this is a little bit of admin work if the lists of such "privileged readers" gets long, but each user would have his/her individual password (even the same as for access to his/her "own" logbook).
Perhaps you can give it a try. |
What a great solution, thanks Yoshio, it works a treat. |
Is there any way to give a logged in user a 'Guest' view on certain logbooks?
Unfortunately at the moment if they are not in the 'login users = ' group they are automatically logged out and have to re-log back into their own logbook. |
I have this same issue. People come and go from one logbook to the other but I still want them to maintain logged in status to the logbook they have rights to. |
|
Re: Multi Logook Login, posted by Hal Proctor on Tue Apr 14 20:03:06 2009
|
| Grant Jeffcote wrote: |
|
|
Hal Proctor wrote:
|
|
We have two logbooks, each with a different list of users.
The logbooks are open to all network users for read only.
A user with Write permisions logs into his designated logbook.
He then decides to view the other logbook, the one he does not have write permissions to by clicking on the tab to the other logbook.
He is immediately logged out of the logbook he has write permissions to.
He did not close his browser session, only clicked on the other logbook tab.
Is there Any way to keep that person logged into the logbook he has rights to without having the "keep me logged in Checkbox"?
Just like this site has Forum, Config Examples, etc.
Once you select another tab they are logged out of their logbook they just logged in to.
|
Have a look at this thread Hal, worked well for me: Link
|
thanks Grant, but I dont see the solution. your last entry still states users being logged out when switching logbooks.
Are you suggesting that every user within our orginization needs to be on the deny list of logbook1 if they have rights to logook2? |
|
Re: Multi Logook Login RESOLVED, posted by Hal Proctor on Tue Apr 21 20:32:10 2009
|
| Stefan Ritt wrote: |
|
| Hal Proctor wrote: |
|
| Grant Jeffcote wrote: |
|
|
Hal Proctor wrote:
|
|
We have two logbooks, each with a different list of users.
The logbooks are open to all network users for read only.
A user with Write permisions logs into his designated logbook.
He then decides to view the other logbook, the one he does not have write permissions to by clicking on the tab to the other logbook.
He is immediately logged out of the logbook he has write permissions to.
He did not close his browser session, only clicked on the other logbook tab.
Is there Any way to keep that person logged into the logbook he has rights to without having the "keep me logged in Checkbox"?
Just like this site has Forum, Config Examples, etc.
Once you select another tab they are logged out of their logbook they just logged in to.
|
Have a look at this thread Hal, worked well for me: Link
|
thanks Grant, but I dont see the solution. your last entry still states users being logged out when switching logbooks.
Are you suggesting that every user within our orginization needs to be on the deny list of logbook1 if they have rights to logook2?
|
Can you try the following:
- Put your "password file = xxx" option from the [global] section in elogd.cfg into each individual logook, remove it from [global]
- Remove all cookies from your browser
- Try again to log in to the individual logbooks
The login is handled through cookies. Once you log in, you get two cookies unm (for user name) and upwd (for user password). Each cookie contains a "path" which controls to which URL the browser sends that cookie. If you "password file = xxx" statement is under [global], then "path=/", meaning the cookie is sent for all logbooks. This confuses you if you have different rights for different logooks. If "password file = xxx" is however in each individual loogbooks configuration, then you get "path=/<lobook>". You can check that by inspecting your browser's cookies. In that case the login name and password cookies are only sent to the URL for that specific logbook. I have not tested that extensively (different browsers, with/without Apache proxy), but if it works reliably, I will put this into the documentation.
|
This worked for us just fine! thanks! |
|