Hi Angela, > the security provider is IMO just a temporary solution > in order to have a quick way to setup the system. there will > for sure be major refactoring in terms of configuration, initial > content, commit hooks, validation and so forth... > i don't see to much benefit in putting a lot of effort in this > right now
I wanted to use the new configuration support in SecurityProvider to customize the user and group home paths (as I have them hardcoded in my fork). So for now I would create the SecurityProvider instance directly -> configure it -> pass it to ContentRepositoryImpl. regards Chetan
