Win a copy of Testing JavaScript Applications this week in the HTML Pages with CSS and JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
Bartenders:
  • Piet Souris
  • Frits Walraven
  • Carey Brown

RMI Security Policy

 
Ranch Hand
Posts: 73
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The search brought back many loosely related topics but couldn't find this specifically...

So I have an RMI application that works fine when using the below security policy file:



Now I'm ready to deliver it to clients and I'd like to lock it down to the path that the code resides in. The below policy:



Allows the server to start properly, but as soon as a client attempts to connect, the server reports:




So following some of the examples online I also tried the policy:



This one doesn't even allow the server to start. The server reports:



Can someone help explain what I may be doing wrong here? Is there anything else I need to provide to help explain why I'm getting these results? Thanks!!
 
Greenhorn
Posts: 14
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
do simple thing
run policytool on command prompt.

set 'Allpermissions' in it and save the file in user directory, with name '.java.policy'.

then try to run your server. i think this will resolve your problem
 
Shawn Kuenzler
Ranch Hand
Posts: 73
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks abhishek!

This works, but I have a couple concerns.

1) Isn't this process just creating a policy file that supersedes the one I really want to use for my application? .java.policy looks like my wide open security policy I used for testing...



2) I don't want to have customers copy a this policy file to their home directory. I'd rather have my entire application contained within the .jar
 
Shawn Kuenzler
Ranch Hand
Posts: 73
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Anyone?
 
abhishek jethwani
Greenhorn
Posts: 14
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
hi shawn,

for your query i have to code and see, mean while if you get some solution please update me too.

thanks
 
Consider Paul's rocket mass heater.
    Bookmark Topic Watch Topic
  • New Topic