- Before that change on each requests 4x we loaded plugins for authentication, this hit
many caches, db invalidation context and loaded the plugins logic each time. This was a heavy performance hit
for SVN and other backends as they needed to load that plugins many many times
- Since Authentication plugins almost never change, we'll not store the plugins listed for authentication into
the authnregistry for each process
- For AuthPlugins settings we now also flush plugins settings, and authnregistry cached plugins
- we had many requests from admins on doing so, after connecting LDAP/Saml
- since admins actually started doing this via DB it's no longer a point we shouldn't enable it via UI
- previous implementation had a bug that cached the settings in each class, caused not refreshing
the update of settings in multi-worker mode. Only restart of rhodecode loaded new settings.
If you set 'rhodecode.auth_plugin_fallback = egg:rhodecode-enterprise-ce#rhodecode'
in your INI file the rhodecode auth plugin is always appended to the list of plugins
that are used for authentication.
