User Ratings

★★★★★
★★★★
★★★
★★
23
0
0
0
2
ease 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 0 / 5
features 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 0 / 5
design 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 0 / 5
support 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 0 / 5

Rate This Project
Login To Rate This Project

User Reviews

  • Nice work ! Great project.
    1 user found this review helpful.
  • Mod-auth-sspi is great! Thanks.
    1 user found this review helpful.
  • Thanks for so usefull software.
    1 user found this review helpful.
  • Thanks for Mod-auth-sspi, it's perfect!
    1 user found this review helpful.
  • make fails . This seems to be a Windows-only solution but it's not mentioned on the project mod_auth_sspi-1.0.4]# make Makefile:11: *** missing separator. Stop.
  • Best project! Perfect for my needs!
  • It's a very nice program
  • Very good tool...
  • Nice!
  • great tool
  • After a new installation of windows one of the first tools i always install
  • I'd like open source software.
  • Excellent piece of work.
  • Very, very light program, and fully featured.
  • not the best in-town any more ;)
  • nice work mate!
  • Awesome job, thanks a lot for showing
  • I have been using it for years, it works very well
  • thanks for the app
  • excellent application.
  • Beautiful work! It works simply by downloading, save into Apache's module folder, paste sample config. That's all!
  • getting damn problems with 1.0.4... someone should update this module !!!
  • Beautiful Work! I developed a SPNEGO authentication with Tomcat on codeplex. I had the same issue with the POST, IE and NTLM, but never with Kerberos. I fixed the program. To not have the issue with POST and IE with mod_auth_sspi, use only Kerberos. To do that: 1) add the parameter SSPIPackage Negotiate 2)launch Apache as a service with the account SYSTEM, or, better, Network Service. So the user can use the service principal name defined on the account of your server(HOST/<name of the server> 3)Your clients must use only the name of your server, not the address. To do that, use a Virtual Host by name. Remark: if the client (IE or Firefox) is on the same computer than apache, you will never use Kerberos.
  • my svn instalation depends on this module ... thanx
  • Great! This module(1.0.4 now) makes svn user authentication by Windows domain a breeze. You just add your apache machine to your Wnidows domain, and write some solid directives in httpd.conf according to TortoiseSVN 1.6.x manual, then you're done. Users can be authenticated via Windows domain, but domain groups seems still to be a problem. We cannot use ''@groupname = rw'' in svn-authz-file .
  • Previous
  • You're on page 1
  • Next