| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
66434
|
Mon Jul 6 07:48:09 2009 |
 | Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.3-2058 | Re: Password recovery setup |
| Ed Strohak wrote: |
|
I'm trying to use gmail to send password recovery e-mails, I get this error when I submit the email address.
"Error sending Email via "smtp.gmail.com": 5.7.0 Must issue a STARTTLS command first. 2sm5111524agd.34"
Any help or insight would be appreciated.
Ed...
|
gmail uses TLS (Transport Layer Security) for the mail communication, which is currently not supported by elog. |
|
65878
|
Mon May 12 10:16:21 2008 |
 | Grant Jeffcote | grant@jeffcote.org | Question | | 2.7.3-1024 | Access Control | Hi Stefan,
We have a configuration where different sites have their own logbooks all under the same server, these are accessed by relevant parties as you might expect by selecting the appropriate tab at the top of the page.
Everyone has visibility of everyone elses logbook as a guest but we have purposely limited the 'Guest' users view (hiding the text portion etc) for various reasons.
We would now like to allow certain parties to view certain logbooks in their entirety but with a 'Read Only' view, I see this can be done but only using a common password. (Read password = <encoded password>)
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. Also if they click on the tab for a logbook that they are not a 'User' for they are logged out of their existing logbook forcing them to have to log back on. If they are designated in a 'Read Only' viewers list for that logbook then their existing password would presumably be read from the global password file and they wouldn't be logged out?
I would like to be able to implement a 'Read' access view for some parties but not have a common password (use the password file?) and not force the other party to re-logon to view the other logbook.
Something like the ability to add a "Read user = <user list>" in each logbook as can be done with 'Login User' and 'Admin User' at present would be great.
Could you let me know if this is feasible please?
Many thanks in advance. |
|
65879
|
Tue May 13 16:58:40 2008 |
| Yoshio Imai | | Question | | 2.7.3-1024 | Re: Access Control |
| 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. |
|
65880
|
Tue May 13 21:56:30 2008 |
| Grant Jeffcote | grant@jeffcote.org | Question | | 2.7.3-1024 | Re: Access Control |
| 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. |
|
65882
|
Thu May 15 17:45:44 2008 |
| Grant Jeffcote | grant@jeffcote.org | Question | | 2.7.3-1024 | Re: Access Control |
| 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. |
|
66312
|
Tue Apr 14 20:00:08 2009 |
| Hal Proctor | hproctor@mpm.com | Question | Windows | 2.7.3-1024 | Re: Access Control |
| 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. |
|
65758
|
Tue Feb 26 03:06:06 2008 |
 | Uwe | uweho@web.de | Question | Windows | 2.7.3 | Problem updating from 2.7.2 to 2.7.3 | Hello,
I am trying to update from version V2.7.2-2041 to V2.7.3 but getting the attached error message. OS is Windows 2003. I installed the update on Windows XP without a problem. Does anybody know ho to solve that problem? Thanks!
Uwe
|
| Attachment 1: error.JPG
|
|
|
65759
|
Wed Feb 27 03:46:28 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.3 | Re: Problem updating from 2.7.2 to 2.7.3 |
| Uwe wrote: |
|
Hello,
I am trying to update from version V2.7.2-2041 to V2.7.3 but getting the attached error message. OS is Windows 2003. I installed the update on Windows XP without a problem. Does anybody know ho to solve that problem? Thanks!
|
The shared library msvcr71.dll should be part of the operating system and placed under c:\windows\system32\msvc71.dll. If not it can be downloaded from
http://www.dlldump.com/download-dll-files.php/dllfiles/M/MSVCR71.dll/download.html |
|