As a Marketplace Developer, I would like to specify PACL policies for allowed socket connections using wildcards, so that my app can deploy to unknown environments successfully

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 6.1.1 CE GA2, 6.1.20 EE GA2
• Fix Version/s: 6.1.X EE, 6.2.0 CE M4
• Component/s: Security, Security > PACL
• Labels:
  • mp
• Branch Version/s:
  6.1.x
• Backported to Branch:
  Committed
• Similar Issues: Show 5 results ; ;

  LPS-34734	As a liferay plugin developer from a unreliable network, I would like to be able to specify my own nexus repositories in ivy-settings.xml
  LPS-35418	As a plugin developer, I wish to have certain scripts executed when my plugin is deployed
  LPS-34664	PACL - As a plugin developer I would like to see DEBUG logging enabled for GeneratingPACLPolicy by default
  LPS-32200	As a Liferay Marketplace Developer, it should be less time consuming and less error prone to identify and declare necessary PACL declarations
  LPS-33047	PACL - As a developer I would like reasonable java operations such as classloading, reflection, native library access within libraries I include to not prevent me from developing plugins for the marketplace

My app requires the ability to contact other servers, so with PACL I can declare:

security-manager-sockets-connect=somehost.com:8080

But users of my app will have their own hostnames, so I need to be able to declare the hostname/IP using wildcards as described in the Java 6 Documentation: http://docs.oracle.com/javase/6/docs/api/java/net/SocketPermission.html