update to 2.3.x, minor API and test adjustments
security fixes: use GeoServerUser, fix tests

securedaccesstests were disabled probably from the initial port
to the new security system. much of this commit fixes that but also
adjusts the cookie filter to be before the anonymous filter. instead
of just using a string for credentials, we use a GeoServerUser
follow up to d3b84999, log auth, adjust tests + db client
fix mix up with principal/credentials
Change extension version to match geoserver version
Comment out war plugin for now
add wps dependency
fix test broken by changing to GeoserverUser
add config for jetty-runner
Merge branch 'master' into 2.3.x
fix test breakage related to ba823b61
Merge branch '2.3.x' into mapstory-2.3.x
2.3 datadir - refresh config
pom - remove war from package phase

to build the war, specifically call the war:war target
2.3 integration - fix geoserver filter chain config

add geonodeCookieFilter to first in chains
add geonodeAnonymousFilter before anonymous 'default' chain
2.3 integration - use admin role from static field

as opposed to resolving from roleService which might
return an incorrect role
2.3 integration - fix form login in gs web admin

this handles the case where an anonymous geonode session exists but
the user is trying to login via the web form. The password auth
will work but then the cookie filter will see the session key and
reauthenticate as anonymous
Merge pull request #10 from kzusy/2.3.x

2.3.x
grab details from acls and pass along
security integration fixes, cleanup + tests

- remove use GeoNodeDataAccessManager.getAdminRole and refactor to
  direct use of GeoServerRole.ADMIN_ROLE
- add AUTHENTICATED_ROLE to credentials in dbclient (at least we're
  consistent w/ default client but not sure needed)
- speed up DefaultSecurityClientTest by many times
- do not attempt to authenticate internal geoserver root user - some
  geoserver internal calls use this for other checks
- some imports cleanup