hi tyson the 'SecurityProvideImpl' has been replaced by a more robust approach that makes sure the 'SecurityProvider' on gets registered as service once all mandatory security modules are ready. this also allows assert that the repository gets properly initialised.
you may find additional information in the following documentation section: http://jackrabbit.apache.org/oak/docs/security/introduction.html the 'SecurityProviderRegistration' is key to the understanding of security related OSGi setup, while the 'SecurityProvideImpl' only remains in the code base for non-OSGi setups such as we have in the unit tests. hope that helps angela On 22/04/16 12:42, "Tyson Bowman" <[email protected]> wrote: >Hi all >I am trying to extend the SecurityProvider and PermissionProvider for a >project and the code was working prior to them upgrading their oak >version. >After some investigation it appears that class was removed as a service >and >the registration class was added. There doesn't seem to be much >documentation or explanation or this change and would love some advice or >examples of how to ensure your security provider gets registered. Also >there have been a few comments about this causing problems for others so >hopefully this can be helpful for others as well. > >This change >https://github.com/apache/jackrabbit-oak/commit/81614454d9b21977ad1930c714 >41ad8f577fe013#diff-8914e351c2be2e543280ae9c9ba54770 > > >Thanks > >Tyson
