Problem:
- Product Name: BES AppServer
- Product Version: 5.x and above
- Product Component: Security
- Platform/OS Version: All
A client executing within the Borland J2EE Client Container (appclient) attempts to invoke a method (e.g. create() ) on a secured EJB (or CORBA service) and instead of being prompted to authenticate itself (e.g. with a username and password), will instead receive the following exception:
Client Container Error: Caught unhandled exception from client application
java.rmi.AccessException: CORBA NO_PERMISSION 1447174912[];
nestedexception is: org.omg.CORBA.NO_PERMISSION: minor code: 1447174912 completed: No org.omg.CORBA.NO_PERMISSION: minor code: 1447174912 completed: No
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:232)
at com.inprise.vbroker.orb.SE.read(SE.java:28)
at com.inprise.vbroker.orb.DelegateImpl.handleReply(DelegateImpl.java:800)
at com.inprise.vbroker.orb.DelegateImpl.invoke(DelegateImpl.java:686)
at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:454)
at com.borland.examples.ejb.shoppingcart._CartHome_Stub.create(_CartHome_Stub.java:52)
at com.borland.examples.ejb.client.CartClient.main(CartClient.java:27)
at java.lang.reflect.Method.invoke(Native Method)
at com.borland.appclient.Container.invokeAppClientMain(Container.java:201)
at com.borland.appclient.Container.main(Container.java:170)
Resolution:
This problem arises when the client has not specified a Callback Handler in its application-client.xml descriptor.
To solve this, use the Deployment Descriptor editor to open the client.jar file, and in the General tab, insert the class name of a callback handler (e.g. com.borland.security.provider.authn.HostCallbackHandler).
#BorlandApplicationServer
#AppServer
#VisiBroker
#ApplicationServer
#Security
#NO_PERMISSION
