Locking a Thread, posted by Hal Proctor on Wed Feb 13 15:39:07 2013
|
How can I set up the admins or manager group with the ability to Lock a Thread? I don't wish to keep two log books. |
Re: Locking a Thread, posted by Hal Proctor on Wed Feb 13 16:56:40 2013
|
| Stefan Ritt wrote: |
|
| Hal Proctor wrote: |
|
How can I set up the admins or manager group with the ability to Lock a Thread? I don't wish to keep two log books.
|
With
allow <command> = <user list>
deny <command> = <user list>
you can prevent certain users to use certain commands (like delete a message). If you only allow admins to issue the "edit" command, that would in principle do it, but then normal users cannot edit their entries any more. Unfortunately this command cannot be restricted to certain attributes, like the thread "status". So I guess what you want is not exactly possible with the current implementation.
|
Thanks for the reply. I was looking for a way to stop replies to a runaway thread. Was wondering why the elog system has a "Locked by" attribute, but no way to set it. |
|
Kerberos on VM server 64bit, posted by Hal Proctor on Thu May 2 21:10:23 2013
|
I have a logbook installed on a Windows 64 bit VM server 2008 R2 and can access it fine using the password file. However when using Kerberos it does not authenticate correctly. I installed Kerberos and pointed it to the realm an domain controller. Using KINIT command line it appears to accept my password. Any help is appriciated. Perhaps some other diagnostics i could try against the kerberos install
Here is global settings:
port = 49212
ssl = 1
url = https://my-elog.domain.com:49212/
Authentication = Kerberos, file
Kerberos Realm = DOMAIN.COM
Admin User = me
Max content length = 10485760
Password file = pw.txt
Allow password change = 1 (perhaps this is an issue???)
Also...when adding users to the logbook, do you leave the password blank if using Kerberos? |
|
Re: Kerberos on VM server 64bit, posted by Hal Proctor on Fri May 3 19:09:45 2013
|
| Stefan Ritt wrote: |
|
| Hal Proctor wrote: |
|
I have a logbook installed on a Windows 64 bit VM server 2008 R2 and can access it fine using the password file. However when using Kerberos it does not authenticate correctly. I installed Kerberos and pointed it to the realm an domain controller. Using KINIT command line it appears to accept my password. Any help is appriciated. Perhaps some other diagnostics i could try against the kerberos install
Here is global settings:
port = 49212
ssl = 1
url = https://my-elog.domain.com:49212/
Authentication = Kerberos, file
Kerberos Realm = DOMAIN.COM
Admin User = me
Max content length = 10485760
Password file = pw.txt
Allow password change = 1 (perhaps this is an issue???)
Also...when adding users to the logbook, do you leave the password blank if using Kerberos?
|
You can leave the password just blank.
The "Allow password change = 1" does not make any difference. It works here even with this option.
So I have no idea why you have that problem. Does it work on another computer, i.e. is it related to the 64 bit VM machine?
Best regards,
Stefan
|
The kerberos install, installed the Network Identity Manager and placed krb5 config in my windows directory. Can a server run lsass.exe only? or does the krb5 config file and Network Identity Manager need to be on the server?
|
|
Re: Kerberos on VM server 64bit, posted by Hal Proctor on Fri May 3 19:27:53 2013
|
| Hal Proctor wrote: |
|
| Stefan Ritt wrote: |
|
| Hal Proctor wrote: |
|
I have a logbook installed on a Windows 64 bit VM server 2008 R2 and can access it fine using the password file. However when using Kerberos it does not authenticate correctly. I installed Kerberos and pointed it to the realm an domain controller. Using KINIT command line it appears to accept my password. Any help is appriciated. Perhaps some other diagnostics i could try against the kerberos install
Here is global settings:
port = 49212
ssl = 1
url = https://my-elog.domain.com:49212/
Authentication = Kerberos, file
Kerberos Realm = DOMAIN.COM
Admin User = me
Max content length = 10485760
Password file = pw.txt
Allow password change = 1 (perhaps this is an issue???)
Also...when adding users to the logbook, do you leave the password blank if using Kerberos?
|
You can leave the password just blank.
The "Allow password change = 1" does not make any difference. It works here even with this option.
So I have no idea why you have that problem. Does it work on another computer, i.e. is it related to the 64 bit VM machine?
Best regards,
Stefan
|
The kerberos install, installed the Network Identity Manager and placed krb5 config in my windows directory. Can a server run lsass.exe only? or does the krb5 config file and Network Identity Manager need to be on the server?
|
Installed both on a Windows 2003 R2 server (32bit) and Kerberos not authenticating, yet gievs me a ticket thru kinit. |
|
Kerberos on Windows server, posted by Hal Proctor on Mon May 13 16:44:05 2013
|
Does anyone have a success story with kerberos on windows? |
|
Multi Language based on logged on user?, posted by Hal Proctor on Thu May 16 15:41:34 2013
|
Can ELog support different languages based on the logged on user? |
|
Re: Kerberos on Windows server, posted by Hal Proctor on Thu May 16 16:29:16 2013
|
| Hal Proctor wrote: |
|
Does anyone have a success story with kerberos on windows?
|
Anyone? Bueller? |