Watch, Follow, &
Connect with Us

Please visit our new home
community.embarcadero.com.

Public Report
Report From: JBuilder 2007/DSIB - Liferay configuration    [ Add a report in this area ]  
Report #:  49242   Status: Reported
ProjectAssist users not added to svn-auth-file
Project:  JBuilder 2007 Build #:  v20061116_0221
Version:    2007 1.0 Submitted By:   Ervin Czimskey
Report Type:  Basic functionality failure Date Reported:  7/18/2007 1:38:17 PM
Severity:    Infrequently encountered problem Last Updated:
Platform:    Windows XP Internal Tracking #:  
Resolution: None  Resolved in Build: : None
Duplicate of:  None
Voting and Rating
Overall Rating: No Ratings Yet
0.00 out of 5
Total Votes: None
Description
After creating and installing an initial project in ProjectAssist with a single Admin user, adding additional users fails to grant those users access to the subversion repository.  They are set up correctly for the other tools in the ProjectAssist stack.
Steps to Reproduce:
1.  Create a new, standard ProjectAssist installation, with a single Admin user.
2.  For the Project Content Provider, select Existing Project Directory and provide a source folder path.
2.  Install the .pacx file on the server machine.  Confirm that the Admin can access svn and the code that was specified in the project content directory is uploaded to svn.
3.  Save and close the .pacx file.
4.  Re-open the .pacx file in ProjectAssist2007, and clone the Admin.  For kicks, add a separate non-Admin user.
5.  Save the .pacx file and press the Install ProjectAssist ('Do It Now') button.
6.  Confirm that the new Admin and User can login successfully to Liferay, Bugzilla, etc but they cannot Commit to the svn repository.
Workarounds
You can manually grant additional users access to the svn repository by adding their userID/password pair to the svn-auth-file using the htpasswd.exe tool.

The tool is located in the /Apache2/bin folder created by ProjectAssist, and the svn-auth-file is located in the /Apache2/conf folder.  Use the -m option (which is the default behavior) to encrypt the password, rather than storing it in plain text.
Attachment
None
Comments

None

Server Response from: ETNACODE01