i've been having issues where calls to the LogonUser Windows API function is falling back to NTLM authentication, rather than using the preferred, default, Kerberos authentication.
Researching the problem, a guy has a suggestion:
The thing to do is to figure out why the code is using NTLM instead of
Kerberos in the first place since Kerberos is the default and to try to see
if it can be
I've setup public key authentication for ssh'ing into my university machine. However, it only logs me in on the local machine and doesn't give me Kerberos credentials which I need for accessing my network folder.
I have a web application (hostname: service.domain.com) and I wish to use Kerberos authentication to identify users that are logged into a Windows domain. Microsoft AD (Windows Server 2008 R2) is providing the Kerberos service.
The service is a Java web application using Spring Security Kerberos extension library to implement SPNEGO/Kerberos protocol.
Hi ,
I tried to configure nis with kerberos authentication, and i think i configured my server correctly coz i already configured nis with kerberos earlier and it was working fine but not today i getting error.
I'm trying to test a Kerberos-based SSO solution for our Java app. Unfortunately, I don't have a Windows domain at my disposal to do so.
I have installed a Kerberos KDC on Fedora 16 and using keytab authentication for all the linux clients.
Now I want to add a windows client for my linux KDC, can someone please suggest how to set up a windows 2008 machine as a kerberos client for Linux KDC.
Thanks,
-Chhavi
[This question is not about getting your LDAP password to authenticate you for SSH logins. We have that working just fine, thank you :-) ]
Let's suppose you're on a Linux network (Ubuntu 11.10, slapd 2.4.23), and you need to write a set of utilities that will use ldapmodify, ldapadd, ldapdelete, and so on.
Hi!
I have set up a 389 DS server and a kdc . However there is not a howto or any document concerning setting up the DS as a Kerberos database back-end. Nor is there a 389 DS forum, so I am asking here and hopefully some of you could possibly help or throw in some light as to this kind of setup.
I followed this Kerberos-on-Firefox procedure but still Firefox does not connect via the company's Kerberos.
I am using Firefox 3.0.18 on RedHat EL Server 5.5
Here is what I did:
Run kinit on the command line to create a Kerberos ticket
Check with klist: the ticket is valid until tomorrow, service principal is krbtgt/DC.THECOMPANY.COM@DC.THECOMPANY.COM.
In Firefox, set network.negotiate-auth.t