There are several approaches, for example:
1. To keep the build file.xml.example (turnips)
In this case, each developer has to copy it with the name build.xml by changing the settings as desired, and he himself build.xml added to .svnignore, not to grind the values of the individual developers and has always been an example config.
2. Sometimes, doing so build.xml (turnips) stores common to all settings, and to override or add each developer need to create your build.xml.local, which is listed in the blacklist repository. Of course, when you connect configs that must be taken into account, and you want validation to occur on the local configuration.
3. The approach I find most successful, used in many framwork, not only php, for example in the Zend, Symphony and rails, Django, — when one config has multiple partitions, with the possibility to inherit settings from other sections, each individual section can be presledovanie and extended/updated Sections are connected depending on environment variable.
And Yes, answering the question, store the access settings in the repository is fine, unless of course it is not the public rap for the overall fit of the 1st and partly the 2nd methods.