FilterChainManagerProvider implements Mediator<Named,Filter,FilterChainManager> so the key used to register it as a Mediator should match, ie. Key.get(Filter.class,Named.class) ... Alternatively the key could have been left as Key.get(Filter.class) and the type parameters changed to Mediator<Annotation,Filter,FilterChainManager>, but then you'd need a way to map any old Annotation to a filter-name
Merge pull request #24 from sonatype/fix-mediator-registration

PENDING: Fix mediator registration
NXCM-4884: Reworked Kenai realm according to AuthAPI

Wiki:
https://kenai.com/projects/kenaiapis/pages/AuthAPI

It uses the
```
POST /api/login/authenticate.json
Content-Type: application/x-www-form-urlencoded
username={user}&password={pass}
```
form.

The mock KenaiMockAuthcServlet also adapted.
NXCM-4884: Stripped off authz completely.

As for one, it never worked. As for two, this was
the reason (swallowed JSONException) that prevented
proper login to happen.

authz with newly introduced POST was working, but
building the role list failed, as Kenai does
not answers what authz code in this realm was
expecting (a JSON string). for now, simply
the default role (set in kenai XML config)
is returned.
Merge pull request #27 from sonatype/nxcm-4884-kenai-realm-broken

[REVIEW] NXCM-4884: Reworked Kenai realm according to AuthAPI
WIP: ConfigurationManager thread-safety
Start using ConcurrentConfigurationManager interface
Kenai Realm removed from Security.

Is part now of Nexus OSS:
https://github.com/sonatype/nexus/pull/839
Update ConfigurationManager with thread-safe methods

Merge ConcurrentConfigurationManager interface into ConfigurationManager
interface. This will force all clients to start using new thread-safe
ConfigurationManager methods.

DefaultConcurrentConfigurationManager is now the new "default"
ConfigurationManager. It simply adds concurrency, while delegating to
ResourceMergingConfigurationManager, which still delegates to the old
default ConfigurationManager (DefaultConfigurationManager)
Use thread-safe ConfigurationManager methods

Ensure that all users of ConfigurationManager are using "default", and
update usage to use new thread-safe methods
Update tests

Update tests to use DefaultConfigurationManager directly. Arguably,
these should be changed to use DefaultConcurrentConfigurationManager,
but they were never updated to use ResourceMergingConfigurationManager
when that was introduced, and the intent of the tests is to test the
functionality in DefaultConfigurationManager, not
DefaultConcurrentConfigurationManager
Update security version to 3.1-SNAPSHOT

Bumped minor version due to changes to ConfigurationManager interface
Delete obsolete files
Beef up comments on new ConfigMgr methods
ConfigurationManager concurrency tests

Tests for DefaultConcurrentConfigurationManager
Fix license header
Changes based on feedback

Changes from pull request feedback. The big change here was to remove
the type parameters from ConfigurationManager runRead and runWrite
methods, and ConfigurationManagerAction run method. This solution was
compiling and working on Windows, but does not compile on Linux/OSX,
most likely due to a bug in Java 1.6
Merge remote-tracking branch 'origin/master' into security-concurrency

Conflicts:
	security-realms/security-kenai-realm/pom.xml
Remove redundant synchronized method

DefaultConcurrentConfigurationManager now protects access to the save
method. No need for this method to be synchronized
Log lock timeout value