alena 41e5e38fef bug 9336: securityGroups can be used by other securityGroups in the same domain only; no cross domain SG authentication ... status 9336: resolved fixed Following changes were made: * deleteSecurityGroup/authorizeSecurityGroupIngress - removed account/domainId parameters as SG is uniquely identified by id now * removed account_name field from securityGroup DB table; removed allowed_security_group/allowed_sec_grp_acct from security_ingress_rule. These values were used for api response generation only for performance purposes; added caching on API level to improve performance * Added missing security checks for securityGroups/ingressRules		2011-04-22 11:35:29 -07:00
..
doc	Add license header to files	2011-04-14 11:23:14 -07:00
response	bug 9336: securityGroups can be used by other securityGroups in the same domain only; no cross domain SG authentication	2011-04-22 11:35:29 -07:00
ApiDBUtils.java	bug 9336: securityGroups can be used by other securityGroups in the same domain only; no cross domain SG authentication	2011-04-22 11:35:29 -07:00
ApiDispatcher.java	Throw server api exception with correct error code	2011-04-18 16:59:55 -07:00
ApiGsonHelper.java	Add license header to files	2011-04-14 11:23:14 -07:00
ApiResponseHelper.java	bug 9336: securityGroups can be used by other securityGroups in the same domain only; no cross domain SG authentication	2011-04-22 11:35:29 -07:00
ApiSerializerHelper.java	Add license header to files	2011-04-14 11:23:14 -07:00
ApiServer.java	Transform InvalidParameterValueException and PermissionDeniedException to proper API exceptions	2011-04-19 17:07:05 -07:00
ApiServlet.java	bug 9336: securityGroups can be used by other securityGroups in the same domain only; no cross domain SG authentication	2011-04-22 11:35:29 -07:00
ResponseObjectTypeAdapter.java	Add license header to files	2011-04-14 11:23:14 -07:00