[keycloak-user] Strange Redirect Behavior When Upgrading to Version 2

[KevinO]

I've finally go around to upgrading my keycloak server. Everything seems to
be working correctly until I try and view Users in the management portal.

When I try and view a users, it opens the right page but then immediately
redirects to a brute-force url. However, I do not have attack-detection
turned on.

Any idea what configurations I have incorrect.

Keycloak v 2.3.0.Final

http://localhost:8070/auth/admin/realms/External/attack-detection/brute-force/usernames/10052

23:33:44,681 INFO  [org.wildfly.extension.undertow] (ServerService Thread
Pool -- 52) WFLYUT0021: Registered web context: /auth
23:33:44,703 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 47)
WFLYSRV0010: Deployed "keycloak-server.war" (runtime-name :
"keycloak-server.war")
23:33:44,763 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060:
Http management interface listening on http://172.27.0.4:9990/management
23:33:44,763 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051:
Admin console listening on http://172.27.0.4:9990
23:33:44,763 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025:
Keycloak 2.3.0.Final (WildFly Core 2.0.10.Final) started in 13304ms -
Started 425 of 801 services (542 services are lazy, passive or on-dem
and)
23:34:24,425 ERROR [org.jboss.resteasy.resteasy_jaxrs.i18n] (default
task-29) RESTEASY002010: Failed to execute: javax.ws.rs.NotFoundException:
RESTEASY003210: Could not find resource for full path: http://local
host:8070/auth/admin/realms/External/attack-detection/brute-force/usernames/10052
        at
org.jboss.resteasy.core.registry.SegmentNode.match(SegmentNode.java:114)
        at org.jboss.resteasy.core.registry.RootNode.match(RootNode.java:43)
        at
org.jboss.resteasy.core.LocatorRegistry.getResourceInvoker(LocatorRegistry.java:79)
        at
org.jboss.resteasy.core.ResourceLocatorInvoker.invokeOnTargetObject(ResourceLocatorInvoker.java:129)