Added new feature to OpenNaaS called opennaas-spring-security based
on spring, spring-web, spring-dm and spring-dm-web features,
spring-security bundles and new opennaas-core-security bundle.

Created new opennaas-core-security bundle to publish a security filter
based on Spring Security using Spring DM.

Updated all the REST WS publications: Abstract Capability, Resource
Manager, Protocol Session Manager and vCPE Network Manager to require
new security filter.
Merge branch 'develop' of git://github.com/dana-i2cat/opennaas into feature/security
Change opennaas-core-security version from 0.19-SNAPSHOT to
0.20-SNAPSHOT after merging from upstream/develop in new version.
Simplified pom.xml of opennaas-core-security
Updated OpenNaaS Core Security bundle to include persistence
configuration (using HSQLDB) and SecurityRepository. Now it only
initializes Spring Security ACLs SQL Schema.

Now OpenNaaS Core Security bundle is packaged as mandatory bundle of
OpenNaaS loaded after OpenNaaS Core Persistence bundle and before
OpenNaaS Core Resources bundle.
Merge pull request #592 from logoff/feature/security

Feature/security
Bug resolved: creation of ACL SQL tables into security DB, not
previously created. Added zero user rows (with some errors by now).
Features, repositories and dependencies updated to use Spring Security
3.0.8-RELEASE and Spring 3.0.7-RELEASE and their dependencies.

Bug solved in ResourceManager.getResourceDescriptor(String resourceId).
Now it returns the descriptor when the Resource is present in any
repository.

OpenNaaS Core Security bundle with complete Spring Context with desired
security configuration. New ACLManager that creates ACL DB, fills it
with basic users and allows creating ACLs and ACEs. It is exported as an
OSGi service.

Removed unnecessary tables in security DB. Only ACL tables remain.

New Security iTest.
Users loaded from a properties file located in the OpenNaaS Core
Security bundle.
ACLManager registered as OSGi service in Java code to access ConfigAdmin
OSGi service and extract WS URL property.

Users and roles hardcoded in Spring Security context.

ACLManager WS interface only with GET HTTP Requests and path params.
Merge pull request #605 from logoff/feature/security

Feature/security

New OpenNaaS Core Security bundle created that exports an OSGi service that can be used to secure OpenNaaS Resources and ask for accessibility to them. It is based on Spring Security ACLs engine.

Besides, new integration test created to check correct work of previous bundle.
Make Spring Security SecurityContext available to the application.

    The filter chain now registered doesn't clear SecurityContext to make it available to CXF and to the following service invocation.

    The problem we faced comes from DOSGi not linking registered filter chain with CXF request processing, as explained here:
    https://issues.apache.org/jira/browse/DOSGI-183
    Instead, filter chain is executed before CXF request processing, which normally cleares the context, thus preventing it being accessible when method invocation is triggered.

    To solve this issue, a customised version of org.springframework.security.web.context.SecurityContextPersistenceFilter is used
    SecurityContextPersistenceFilterSkipClearContext
    which lets the user specify if context clearing should be skipped.
    Using it with "skipClearContext" property set to true ensures that SecurityContext will be available in our environment, while DOSGI-183 is not fixed.

    Dependencies order has been changed to force Servlet API version 2.5 is resolved in compilation.

This patch also changes required roles in url filters.
The only role required to call all web services is now ROLE_USER.
Merge pull request #606 from isartcanyameres/feature/security

Make Spring Security SecurityContext available to the application.
Merge branch 'develop' of git://github.com/dana-i2cat/opennaas into feature/security
VCPE extension bundle has now a dependency on Core Security bundle.
Moreover, his Activator make ACLManager OSGi service accessible.
Merge pull request #608 from logoff/feature/security

Feature/security
Secure vCPE Resources fon users on call VCPENetworkManager.create(...)
using ACLManager.
Remove resource if it can not be secured in
VCPENetworkManager.create(...).
Add "admin" user to secured users in VCPENetworkManager.create(...)
Merge pull request #609 from logoff/feature/security

Secure vCPE Resources for users on call VCPENetworkManager.create(...) using ACLManager