wmellors
You're welcome!
So on the authz point, there are two authz files that can used by uberSVN. The standard authz file, set as default will always be updated via uberSVN itself, so there's little point in trying to manually update that outside of the UI. However, the other is the alternative authz file that uberSVN won't interact with. The intent of which is to allow external systems to manage the alternative authz file and not have uberSVN overwrite. However, this would require a certain level of understanding on authz structure, which is why I suggested you experiment outside of uberSVN and get things how you need them, before then layering back into uberSVN.
On Access Control, once deployed the AC trial will require all access and authentication to be prepped by slightly different means. You'll get an additional Access Control tab on the main view, which essentially becomes your window into admin, moving away from the regular uberSVN UI. After AC is deployed, it should also automatically copy all your uberSVN details, so users, repos, teams, etc into the AC environment but you'll then need to go into each AC team and setup resources (structure levels within the repo, as you need) and also rules (allow, deny, read, etc, per user or team). Be aware, however that the trial must run to completion before it will become inactive and your system reverts back to its old self. There's currently no way to uninstall the app, ahead of the trial expiry. As such, I'd suggest setting up a test system somewhere and using that for the AC trial, so as to not affect your production environment too much.
Regards the pricing around a full version of Access Control, it really depends on your needs, such as the amount of users and that kind of thing. If you can let me know some of those kinds of details, I'll forward it onto the Sales team and see if they drop you a line to discuss (if you're OK with that).
Good luck with the dump!
Cheers
Wayne
Eizig
Again, thanks for your answer !
I tried to use the alternate authz file, but I guess it's harder to configure that it looks like, because I didnt' succeed to apply the rights I wanted. Even though I looked at the principal authz file to configure the alternate one...
I also tried the alternative way for the manual dump (dump the whole repository first, then use "svndumpfilter" on the dump file) but it didn't work, I had the same result as when I tried before... I really can't figure out why...
I think I will install another UberSVN on a different server in order to try out Access Control. I will send a PM with some information, it would be great if you could forward it to the sales team !
Thank you once again for your help !