These changes implements the functionality nedeed on MapStore to limit read/write permission on resources by reqesting user's IP address.

The endpoint that permits to specify the new constraint on resources is /rest/resources/resource/{resourceId}/permissions, that now is capable to handle a permission model like the following:

<SecurityRuleList>
    <SecurityRule>
        <canRead>true</canRead>
        <canWrite>true</canWrite>
        <user>
            <id>7</id>
        </user>
        <ipRanges>
            <ipRange>
                <cidr>127.0.0.0/8</cidr>
                <description>home</description>
            </ipRange>
            <ipRange>
                <cidr>192.168.1.1/32</cidr>
                <description>single host</description>
            </ipRange>
        </ipRanges>
    </SecurityRule>
[...]
</SecurityRuleList>

As per the example, an user with an IP address like 127.1.2.3 would have complete access to the resource, since the canRead and canWrite values are true.
Conversely, an user with IP 192.168.1.2, even with the read and write permissions, would not be able to access the resource, so a call to GET rest/extjs/resource/{resourceId}?includePermissions=true will return 403 error.

Documentation updated to describe this new functionality:

• https://github.com/geosolutions-it/geostore/wiki/Authorization-section
• https://github.com/geosolutions-it/geostore/wiki/REST-API#resources