|
Problem(Abstract) |
A CORBA.NO_PERMISSION error occurs in SystemOut.log when
trying to connect to an IBM® WebSphere® Application Server naming service.
Global security is turned on in the WebSphere Application Server
administrative console.
The error stack in SystemOut.log is similar to this:
[9/22/05 15:40:41:895 PDT] 7dc141 Helpers W NMSV0610I: A NamingException
is being thrown from
a javax.naming.Context implementation. Details follow:
Context implementation: com.ibm.ws.naming.jndicos.CNContextImpl
Context method: rebind
Context name: DEVNetwork/nodes/DEV/servers/nodeagent
Target name: server2-2809-NotificationImpl
Other data: Object to bind:
com.inc.businessapp.system.NotificationImpl@15a15f
Exception stack trace: javax.naming.NoPermissionException: NO_PERMISSION
exception caught.
Root exception is org.omg.CORBA.NO_PERMISSION:
Trace from server: 298002686 at host 192.168.2.159 >>
org.omg.CORBA.NO_PERMISSION: not authorized to perform rebind_corba_object
operation.
minor code: 0 completed: No
at
com.ibm.ws.naming.cosbase.WsnOptimizedNamingImplBase.performAuthorizationCheck
(WsnOptimizedNamingImplBase.java:2716) |
|
|
|
Cause |
Failure to authenticate to Application Server in the code
before creating the Initial Context. |
|
|
Resolving the
problem |
To access the name space as an authenticated user, you
must authenticate to WebSphere Application Server in your code before
creating the Initial Context. You need to authenticate to WebSphere
Application Server using Java Authentication and Authorization Service
(JAAS) authentication via the LoginContext.
Example
code for V6.0
Example
code for V5.1
Example
code for V5.0 |
|
|