Skip to main content

SVN: Subversion apache configuration smackdown

All I wanted out of life was to authenticate off Active Directory, have everyone with a valid user be able to read my svn repo and have a build user defined in a file for my Continuos integration (Non active directory user) and have a couple of AD users have read/write permissions sounds simple but maybe not so much.

This is my config file (in /etc/httpd/conf.d):
<AuthnProviderAlias ldap adf-ldap-alias>
#ldap config make sure the DN config is correct and the server is right
  AuthLDAPURL "ldap://adserver.co.za:3268/OU=User Accounts,DC=company,DC=co,DC=za?sAMAccountName?sub?(objectClass=*)" NONE
  AuthLDAPBindDN "svnuser@company.co.za"
  AuthLDAPBindPassword supersecret
</AuthnProviderAlias>

<AuthnProviderAlias file adf-file-alias>
#setup this file using  htpasswd
  AuthUserFile /etc/subversion/adf-auth-file
</AuthnProviderAlias>

<Location /adfrepo>
  DAV svn
  AuthType Basic
  AuthName "ADF Subversion Repository"
#this is where the magic happens for using two providers
  AuthBasicProvider adf-ldap-alias adf-file-alias
#Permissions that dont use AD Groups
  AuthzSVNAccessFile /etc/subversion/adf-authz
#path to your new repo
  SVNPath /usr/local/svn/adf
  Require valid-user
</Location>

Example of /etc/subversion/adf-authz (* = r means everybody has read access)

[groups]
svnAdf = usr1, usr2, bob

[:/]
@svnAdf = rw

[/]
* = r
@svnAdf = rw


Some nifty commands
#add a build user to the auth file
htpasswd -cmd /etc/subversion/adf-auth-file builduser

#copy old repo to new repo
svnsync init http://newsvn.company.co.za/adf http://oldsvn.company.co.za/svn/adf
svnsync sync file:///usr/local/svn/adf
svnadmin setuuid /usr/local/svn/adf
 

#create the new repo with correct permissions
svnadmin create /usr/local/svn/adf
chcon -R -t httpd_sys_content_rw_t /usr/local/svn/adf
chown -R svnadmin /usr/local/svn/adf
chgrp -R apache /usr/local/svn/adf
chmod -R g+w /usr/local/svn/adf

pre commit hook to enforce comments
$SVNLOOK log -t "$TXN" "$REPOS" | grep "[a-zA-Z0-9]" > /dev/null || { echo "Please enter a comment before you commit." >& 2; exit 1; }

Comments

Popular posts from this blog

ADF Encountered deferred syntax #{ in template text.

OracleJSP error: oracle.jsp.parse.JspParseException:  Error: Encountered deferred syntax #{ in template text.  If intended as a literal, escape it or set directive  deferredSyntaxAllowedAsLiteral This normally happens when you have some tag lib dependancy problems but this was  not the case for me... My problem: For some reason my model project had web stuff in it(public html etc)  so I had to remove the public html stuff from my project and manually edit the Model.jpr project file and remove the tag lib entries at the bottom o the file. Go figure.    

JBO-25013: TooManyObjectsException

oracle.jbo.TooManyObjectsException: JBO-25013: Too many objects match the primary key oracle.jbo.Key[Key null ]. Ok so for you it may be trying to insert a duplicate record this should explain your problem (also check trigger they could be the cause.) NOTE: You can also try to create a new duplicate EO if you have a page with two VO's using the same EO. This could sort your problems. For me I needed to add a launch listener on my LOV and clear the cache of my vo. LOV <af:inputListOfValues id="NameId" popupTitle="#{bindings.Name.hints.label}" value="#{bindings.RolName1.inputValue}" label="#{bindings.RolName1.hints.label}" model="#{bindings.RolName1.listOfValuesModel}" required="#{bindings.RolName1.hints.mandatory}" columns="#{bindings.RolName1.hints.displayWidth}" shortDesc="#{bindings.RolName1.hints.tooltip}" launchPopupListener="#{backingBeanScope.backingBean.launchPop

OJDeploy: Documentation for the tool

Real DOCS:  http://docs.oracle.com/cd/E26098_01/user.1112/e17455/deploying_apps.htm#OJDUG645 OJDeploy Documentation if you run it from the command line - I keep looking for this so I though I would post it here so I remeber. Oracle JDeveloper Deploy 11.1.2.1.0.6081 Copyright (c) 2003, 2010, Oracle and/or its affiliates. All rights reserved. Usage:   ojdeploy -profile <name> -workspace <jws> [ -project <name> ] [ <options> ]   ojdeploy -buildfile <ojbuild.xml> [ <options> ]   ojdeploy -buildfileschema Arguments:   -profile               the name of the Profile to deploy   -workspace      full path to the JDeveloper Workspace file(.jws)   -project              name of the JDeveloper Project within the .jws where the Profile can be found. If omitted, the Profile is assumed to be in the Workspace.   -buildfile            full path to a build file for batch deploy   -buildfileschema  print XML Schema for the build file