[#MULE-2792] Security Policy for RMI connector.

Details

Type: Improvement
Status: Closed
Priority: To be reviewed
Resolution: Won't Fix or Usage Issue
Affects Version/s: None
Fix Version/s: None
Component/s: Modules: Security (Spring Security, Acegi, PGP, WS-Security)
Labels:
None

User impact:
High
Similar Issues:
~~MULE-1576~~ Create Schema, Namespace handler and testcase for the RMI / EJB connectors
~~MULE-468~~ Rmi and axis endpoint conflict
~~MULE-1794~~ RMI Method Types
~~MULE-172~~ RMI provider
MULE-3853 Retry Policy ignored if JBoss is not running at startup
~~MULE-3560~~ RMI Receiver does not read "methodArgumentTypes"
~~MULE-3037~~ wsdl-xfire connector (AxisWsdlConnector) failing to invoke secured webservices.
~~MULE-4070~~ EndpointURI password security
~~MULE-1579~~ Create Schema, Namespace handler and testcase for the Email connector
~~MULE-372~~ RMIReceiver for Mule. App-->(RMI)Mule -way

Description

Facing security.policy issue with RMI connector. This is getting solved if i modify the java.policy file in my JRE/lib folder of JDK by granting all permissions. Is there any way by which we can just add the permission for RMI connector without modifying the java.policy file.

Activity

Ascending order - Click to sort in descending order

Hide

Permalink

Mike Schilling added a comment - 18/Oct/10 05:21 PM

Sorry, Mule 1 is no longer supported. If you can reproduce this in a supported version, please enter a new issue.

Show

Mike Schilling added a comment - 18/Oct/10 05:21 PM Sorry, Mule 1 is no longer supported. If you can reproduce this in a supported version, please enter a new issue.

People

Assignee:

Unassigned

Reporter:

Sagar Modi

Vote (0)

Watch (0)

Dates

Created:

11/Dec/07 09:46 AM

Updated:

18/Oct/10 05:22 PM

Resolved:

18/Oct/10 05:22 PM