Granny's Programming Pearls
"inside of every large program is a small program struggling to get out"
JavaRanch.com/granny.jsp
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Junilu Lacar
  • Jeanne Boyarsky
  • Bear Bibeault
Sheriffs:
  • Knute Snortum
  • Tim Cooke
  • Devaka Cooray
Saloon Keepers:
  • Ron McLeod
  • Stephan van Hulst
  • Tim Moores
  • Tim Holloway
  • Carey Brown
Bartenders:
  • Piet Souris
  • Frits Walraven
  • Ganesh Patekar

Authentication with Subversion and Apache

 
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello,
I am trying to configure authentication with Apache for Subversion repository. I have successfully (hopefully as it didn't error out) setup authentication for a user "harry" with corresponding password "test" as shown below:

The file "svn-auth-file" is created in C:\svn_repository\conf too. Since I didn't get any error/s and the file is created, this must be good.

And added the following entries in the httpd.conf file.


I restarted Apache and tried to access the repository with http://localhost/svn, I do get asked for user name and password. Using "harry" and "test" does not work as it just keeps asking me for user name and password. Any idea what I am missing here that Its not working?

Thanks.
T
 
Saloon Keeper
Posts: 21133
134
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Yup. Their documentation isn't precise enough. The svn authentication files are for use with the SVN server. When you're using Apache/DAV as the interface, you set up Apache security, instead.
 
Tim Francisco
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Tim Holloway wrote:Yup. Their documentation isn't precise enough. The svn authentication files are for use with the SVN server. When you're using Apache/DAV as the interface, you set up Apache security, instead.



Ok. I am confused. I thought I did installed SVN server.

Is there a resolution to this though?
 
Tim Holloway
Saloon Keeper
Posts: 21133
134
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
SVN consists of several components, frequently all bundled as a unit.

There's the admin SVN utilities, which set up the archive filesystem structure and maintain the archives.

There's the svn server, which can run either via the Unix superserver (inet) or as a stand-alone daemon.

There's the svn user client utilities, which all users to check projects in and out and commit changes, etc. These utilities can operate against a local archive on a time-shared system (not very common these days), via the svn server, or via HTTP/DAV.

Not generally part of the package:

There's also mod_dav, which is a plugin for the Apache webserver. It allows users to use DAV to talk to Subversion. Other servers such as IIS may have their own plug-ins for the same purpose.

When they do that, the subversion security files are not referenced. Mod_dav uses Apache's security system, so access is controlled as part of the general web access control mechanisms such as the ".htaccess" files and the settings in Apache's httpd.conf files. Which may reference security plugins. Mine uses the LDAP plugin, for example.
 
Tim Francisco
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Tim Holloway wrote:SVN consists of several components, frequently all bundled as a unit.

There's the admin SVN utilities, which set up the archive filesystem structure and maintain the archives.

There's the svn server, which can run either via the Unix superserver (inet) or as a stand-alone daemon.

There's the svn user client utilities, which all users to check projects in and out and commit changes, etc. These utilities can operate against a local archive on a time-shared system (not very common these days), via the svn server, or via HTTP/DAV.

Not generally part of the package:

There's also mod_dav, which is a plugin for the Apache webserver. It allows users to use DAV to talk to Subversion. Other servers such as IIS may have their own plug-ins for the same purpose.

When they do that, the subversion security files are not referenced. Mod_dav uses Apache's security system, so access is controlled as part of the general web access control mechanisms such as the ".htaccess" files and the settings in Apache's httpd.conf files. Which may reference security plugins. Mine uses the LDAP plugin, for example.



Tim Thanks for your constant reply.

I just changed AuthType to Basic from Digest and it works. I changed back to Digest from Basic, and does not work.

There's something that needs to be configured for the Digest to work based on what I am seeing.

 
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!