KM - Java iView - User Authentication

Hello all,
I'm writing a simple KM iView in Java for EP6.0.
I want to experiment with resources; accessing, creating etc.
I use the following code to create my IUser and access the resource context
IUser user = userFactory.getUser(request.getUser().getUniqueName());
IResourceContext resourceContext = new ResourceContext(user);
If I access the resource "/", everything is fine, it gets found and I can display it's children, one of them being "/documents". When I try to access this resource I cannot because "User is not authenticated". I cannot access any other collections for the same reason. I can access a file I've created underneath "/documents", my iView displays that the file was 'found' but I cannot work with the file (e.g. display its content type) because "User is not authenticated".
So how does a user become authenticated? Is this a user mapping issue, something that can be resolved by the portals user administrator, something I can do in Java, or something completely different?
As always, any help is greatly appreciated.
Thanks for your time,
Patrick.

Hey Armin,
Thanks for that, it worked a treat.
I had taken example code from the PDK where creating the IUser was written as
IUser user = .....
I guess they thought that it was so simple they didn't need to write it. I knew that I could access the portal user from the request and then I looked at the API there to see if any methods returned an IUser, that's why I was using getUniqueName(). It seemed to make sense.
One question though, I see that the method for creating the user that you gave me has been deprecated. Has the new method been released or is it on its way, do you know?
Thanks again for the solution. I awarded you the points.
Patrick.

Similar Messages

  • Java card user authentication

    Hi
    Im Using Gemalto TOP DL V2 Java card
    it supports java card 2.2.2 version.
    Will some one guide how to write program to authenticate..
    it support 3DES ,AES encryption
    how i can write user pin inside EEPROM( i hope pin.update )
    what is the use of Mother key they provided with Card?
    Details
    SID A000000003000000

    If you look at the JCDK samples, there is a PIN applet you can look at for user pin.
    What do you want to authenticate? Is it host to applet or host to card manager?
    Cheers,
    Shane

  • Java.lang.SecurityException: Authentication for user system denied in realm wl_realm Error.

              Getting this security exception when trying to pull a message from one weblogic
              instance JMS queue, and sending the message (via a MDB) to another machine's JMS
              queue.
              Ex. Here's the scenario.
              Two Windows2000Server machines,
              one at ip ... xxx.xxx.x.16,
              second machine at ... xxx.xxx.x.17.
              MDB pulls message off of a JMS queue on 16. MDB sends the message to .17 box.
              ON the .17 machine (the receiver) I get the following exception
              weblogic.transaction.internal.CoordinatorImpl@31406b>
              java.lang.SecurityException: Authentication for user system denied in realm wl_realm
                   at weblogic.security.acl.Realm.authenticate(Realm.java:212)
                   at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
                   at weblogic.security.acl.internal.Security.authenticate(Security.java:125)
                   at weblogic.security.acl.internal.Security.verify(Security.java:87)
                   at weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestHandler.java:76)
                   at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:17)
                   at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
                   at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              ON the sending maching .16, I get the following exception.
              ####<Apr 3, 2002 9:46:24 AM CST> <Error> <RJVM> <testweblogic> <OptiSoftAppServer>
              <ExecuteThread: '96' for queue: 'default'> <> <> <000000> <Unsolicited error response
              for: '-1'>
              The messages appear to show up on the destination machine, but are these error
              messages valid, or just bogus?
              Thanks,
              Eric.
              

    Why is that? Your suggestion worked but I don't understand why.
              When our MDB on machineA did the JNDI lookup to MachineB we set the
              credentials to a valid user/password on MachineB.
              My speculation: Since the MDB on machineA is already in a transaction
              any other JNDI calls use the credentials for the MDB's transactions,
              ignoring any other credentials we might try to set explicitly. If my
              speculation is correct then that would explain by the passwords for the
              user "system" would have to be the same between servers.
              Is there a good place to read up on this?
              Thanks
              Tom
              Rajesh Mirchandani wrote:
              > Make sure you have the same system password for the 2 instances of WLS on seperate boxes.
              >
              > Tom Barnes wrote:
              >
              >
              >>Or post to the EJB newsgroup (which "owns" MDBs).
              >>
              >>Tom Barnes wrote:
              >>
              >>
              >>>I think there is a username/password field configurable in the MDB descriptor that
              >>>might help here??? Other than that, I suggest posting to the security newsgroup.
              >>>
              >>>Tom
              >>>
              >>>Eric Babin wrote:
              >>>
              >>>
              >>>>Getting this security exception when trying to pull a message from one weblogic
              >>>>instance JMS queue, and sending the message (via a MDB) to another machine's JMS
              >>>>queue.
              >>>>
              >>>>Ex. Here's the scenario.
              >>>>
              >>>> Two Windows2000Server machines,
              >>>> one at ip ... xxx.xxx.x.16,
              >>>> second machine at ... xxx.xxx.x.17.
              >>>>
              >>>> MDB pulls message off of a JMS queue on 16. MDB sends the message to .17 box.
              >>>>
              >>>>
              >>>>ON the .17 machine (the receiver) I get the following exception
              >>>>
              >>>>weblogic.transaction.internal.CoordinatorImpl@31406b>
              >>>>java.lang.SecurityException: Authentication for user system denied in realm wl_realm
              >>>> at weblogic.security.acl.Realm.authenticate(Realm.java:212)
              >>>> at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
              >>>> at weblogic.security.acl.internal.Security.authenticate(Security.java:125)
              >>>> at weblogic.security.acl.internal.Security.verify(Security.java:87)
              >>>> at weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestHandler.java:76)
              >>>> at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:17)
              >>>> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
              >>>> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              >>>>
              >>>>ON the sending maching .16, I get the following exception.
              >>>>
              >>>>####<Apr 3, 2002 9:46:24 AM CST> <Error> <RJVM> <testweblogic> <OptiSoftAppServer>
              >>>><ExecuteThread: '96' for queue: 'default'> <> <> <000000> <Unsolicited error response
              >>>>for: '-1'>
              >>>>
              >>>>The messages appear to show up on the destination machine, but are these error
              >>>>messages valid, or just bogus?
              >>>>
              >>>>Thanks,
              >>>>
              >>>>Eric.
              >>>>
              >
              > --
              > Rajesh Mirchandani
              > Developer Relations Engineer
              > BEA Support
              >
              >
              >
              

  • Java.lang.SecurityException: Authentication for user guest denied in realm wl_realm

    Hi,
    I am using WL60SP2 on Windows NT 4.0.
    I am trying to call a bean from my startup class. The code is as follows
    home = lookupHome();
    messageSubscriber = (MessageSubscriber) narrow(home.create(),
    MessageSubscriber.class);
    Right at this point the Weblogic server is throwing the following error.
    java.lang.SecurityException: Authentication for user guest denied in
    realm wl_realm
    <<no stack trace available>>
    I know this has something to do with the security. In WL50 I would have
    gone to the weblogic.policy file to fix it. With WL60 I know I have to
    change something on the console but am not sure.
    Please help.
    Thanks
    Raj

    Go into the console and make sure the GuestDisabled property = false
    http://e-docs.bea.com/wls/docs61/////ConsoleHelp/security.html
    Joe Jerry
    Raj Kathlesar wrote:
    Hi,
    I am using WL60SP2 on Windows NT 4.0.
    I am trying to call a bean from my startup class. The code is as follows
    home = lookupHome();
    messageSubscriber = (MessageSubscriber) narrow(home.create(),
    MessageSubscriber.class);
    Right at this point the Weblogic server is throwing the following error.
    java.lang.SecurityException: Authentication for user guest denied in
    realm wl_realm
    <<no stack trace available>>
    I know this has something to do with the security. In WL50 I would have
    gone to the weblogic.policy file to fix it. With WL60 I know I have to
    change something on the console but am not sure.
    Please help.
    Thanks
    Raj

  • Java.lang.SecurityException: Authentication for user null denied in realm

    Hello,
    We have the following exceptionj on WLS 6.1 SP3 on Win2K:
    javax.naming.AuthenticationException. Root exception is
    java.lang.SecurityException: Authentication for user null denied in realm
    weblogic
    at weblogic.security.acl.Realm.authenticate(Realm.java:212)
    at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
    at
    weblogic.security.acl.internal.Security.authenticate(Security.java:135)
    at
    weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialContextFactoryDelegate.java:518)
    at
    weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:362)
    at
    weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:334)
    at
    weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:211)
    at
    weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:149)
    at
    javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:660)
    at
    javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
    at javax.naming.InitialContext.init(InitialContext.java:217)
    at javax.naming.InitialContext.<init>(InitialContext.java:173)
    at
    And it seems that this exception happens after the introduction of a JAAS module
    for an external call.
    What strikes me is that the WLS samples use System.setProperty... and I was wondering
    if this could be the cause of our problem, because the rest of the application
    does not use JAAS, and that may be it screws up the realm with WLS....
    Any idea?
    Cheers,
    Thierry

    Hello,
    We have the following exceptionj on WLS 6.1 SP3 on Win2K:
    javax.naming.AuthenticationException. Root exception is
    java.lang.SecurityException: Authentication for user null denied in realm
    weblogic
    at weblogic.security.acl.Realm.authenticate(Realm.java:212)
    at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
    at
    weblogic.security.acl.internal.Security.authenticate(Security.java:135)
    at
    weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialContextFactoryDelegate.java:518)
    at
    weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:362)
    at
    weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:334)
    at
    weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:211)
    at
    weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:149)
    at
    javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:660)
    at
    javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
    at javax.naming.InitialContext.init(InitialContext.java:217)
    at javax.naming.InitialContext.<init>(InitialContext.java:173)
    at
    And it seems that this exception happens after the introduction of a JAAS module
    for an external call.
    What strikes me is that the WLS samples use System.setProperty... and I was wondering
    if this could be the cause of our problem, because the rest of the application
    does not use JAAS, and that may be it screws up the realm with WLS....
    Any idea?
    Cheers,
    Thierry

  • Java.lang.SecurityException: Authentication for user test1 denied in realm wl_realm

    Environment: WLS61 SP2
    Two WLS61 servers on different machines. User test1 is authenticated against LDAP
    on server_1, then tries
    to execute a class (from JSP) that calls EJB on server_2. The environment properties
    for the call to EJB on server_2 to are setup as follows (Note that user test2 is
    used to call EJB on server_2. User test2 exists in the wl_realm on server2):
    env.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
    env.put(Context.PROVIDER_URL, "t3://server2:7001");
    env.put(Context.SECURITY_AUTHENTICATION, "simple");
    env.put(Context.SECURITY_PRINCIPAL, "test2");
    env.put(Context.SECURITY_CREDENTIALS, "somepass");
    The call results in the following exception raised on server_2. Why is test1 id used
    if test2 is explicitly specified for the call? User test1 does not exist on server_2.
    <Jul 13, 2002 11:37:31 AM EDT> <Warning> <Dispatcher> <RuntimeException thrown by
    rmi server: 'weblo
    gic.rmi.cluster.ClusterableServerRef@111 - jvmid: '4783591120128354231S:xxx.xxx.xxx.xxx:[7001,7001,7002,7
    002,7001,7002,-1]:mydomain:myserver', oid: '271', implementation: '[BaseEJBObject]
    home: c
    om.test.TestEJB_jvjalv_HomeImpl@7583b9''
    java.lang.SecurityException: Authentication for user test1 denied in realm wl_realm
    at weblogic.security.acl.Realm.authenticate(Realm.java:212)
    at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
    at weblogic.security.acl.internal.Security.authenticate(Security.java:125)
    at weblogic.security.acl.internal.Security.verify(Security.java:87)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:237)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

    If you are using JNDI authentication, make sure you close the context before
    you get another context.
    In WLS, stack of authenticated users will be maintained per thread. Now when
    user is authenticated, it will be pushed into the stack. When you close the
    context it will be popped out. In your case it seems like somehow test1 user's
    idenitity is set on the thread which is calling the EJB on server2.
    use weblogic.security.acl.Security.getCurrentUser() to get the current
    user associated with the thread.
    I hope this helps.
    -utpal

  • Java.lang.SecurityException: Authentication for user system denied in realm weblogic

    I am looking for some help to deploy the application in weblogic6.0.
    This is what i did during the application deployment.
    Create a new directory under config as a new application.
    D:\bea\wlserver6.0\config\test
    under test created two other directories applications and logs.
    Under the applications directory copied .ear and .war files.
    Under the test i copied config.xml, all the *.pem starttest.cmd, fileRealam.properties
    files. Modified the config.xml with my application, domain and the server. Modified
    the settest.cmd with the new domain and server name.
    when i do startup, it is prompting for the password and i entered what ever i mentioned
    during the installation.
    And getting the following error.
    Thanks alot for any suggestions.
    D:\bea\wlserver6.0\config\test>startTest.cmd
    D:\bea\wlserver6.0>set PATH=.\bin;D:\bea\jdk130\bin;C:\RATIONAL\RATION~1\NUTCROO
    T\bin;C:\RATIONAL\RATION~1\NUTCROOT\bin\x11;C:\RATIONAL\RATION~1\NUTCROOT\mksnt;
    C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem;C:\Program Files\Dell\Resoluti
    on Assistant\Common\bin;C:\PROGRA~1\MICROS~4\Office;C:\PROGRA~1\ULTRAE~1;C:\Rati
    onal\common;C:\Rational\Rational Test;C:\jdk1.3\bin;C:\Ant\bin;
    D:\bea\wlserver6.0>set CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar
    D:\bea\wlserver6.0>D:\bea\jdk130\bin\java -hotspot -ms64m -mx64m -classpath .;.\
    lib\weblogic_sp.jar;.\lib\weblogic.jar -Dweblogic.Domain=test -Dweblogic.Name=te
    stServer -Dbea.home=D:\bea -Dcloudscape.system.home=./samples/eval/cloudscape/da
    ta -Djava.security.policy==D:\bea\wlserver6.0/lib/weblogic.policy weblogic.Serve
    r
    Enter password to boot weblogic server:password
    Starting WebLogic Server ....
    <Feb 14, 2001 12:13:04 PM EST> <Notice> <Management> <Loading configuration file
    .\config\test\config.xml ...>
    <Feb 14, 2001 12:13:06 PM EST> <Info> <Logging> <Only log messages of severity "
    Error" or worse will be displayed in this window. This can be changed at Admin C
    onsole> test> Servers> testServer> Logging> Debugging> Stdout severity threshold
    >
    <Feb 14, 2001 12:13:08 PM EST> <Emergency> <Server> <Unable to initialize the se
    rver: 'Fatal initialization exception
    Throwable: java.lang.SecurityException: Authentication for user system denied in
    realm weblogic
    java.lang.SecurityException: Authentication for user system denied in realm webl
    ogic
    at weblogic.security.acl.Realm.authenticate(Realm.java:209)
    at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:229)
    at weblogic.security.acl.internal.Security.authenticate(Security.java:11
    3)
    at weblogic.security.SecurityService.initializeSuid(SecurityService.java
    :293)
    at weblogic.security.SecurityService.initialize(SecurityService.java:123
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:343)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
    at weblogic.Server.main(Server.java:35)
    '>
    The WebLogic Server did not start up properly.
    Exception raised: java.lang.SecurityException: Authentication for user system de
    nied in realm weblogic
    java.lang.SecurityException: Authentication for user system denied in realm webl
    ogic
    at weblogic.security.acl.Realm.authenticate(Realm.java:209)
    at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:229)
    at weblogic.security.acl.internal.Security.authenticate(Security.java:11
    3)
    at weblogic.security.SecurityService.initializeSuid(SecurityService.java
    :293)
    at weblogic.security.SecurityService.initialize(SecurityService.java:123
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:343)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
    at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception
    D:\bea\wlserver6.0>goto finish
    D:\bea\wlserver6.0>cd config\test
    D:\bea\wlserver6.0\config\test>ENDLOCAL
    D:\bea\wlserver6.0\config\test>

    Seen this, may give a clue?
    Server Known Problems Change Request Number Description
    042556
    The weblogic.Admin command now requires the user and password options. For example:
    java weblogic.Admin -username system -password gumby1234
    The username "system" is required for most functions (for example: VERSION). If
    you do not specify -username system, you will get the following error:
    Exception in thread "main" java.lang.SecurityException: Authentication for user
    system denied in realm weblogic
    <<no stack trace available>>
    "lazar" <[email protected]> wrote:
    >
    I would also like to know, if there is a fix for it.
    Thanks
    Lazar
    Greg Layton <[email protected]> wrote:
    Did you ever get an answer to this. If so could you share it with me.ThanksGreg

  • Java.lang.SecurityException: Authentication for user system denied in realm wl_realm

    I am experiencing this error when a servlet or JSP is preloaded on the web
    server and the init method of the preloaded item results in a call to the
    app server. If I don't preload and then manually invoke the JSP or servlet
    after the web server completely loads the call to the app server does not
    produce the exception. The only security differences between the web and
    app servers are the console and system passwords. I can fix the problem by
    making the passwords (system and console) the same across the board, but
    find it hard to believe that this is the true solution. I would prefer
    sticking with the default security settings.
    I've poured through hundreds of messages. I can find similar problems but
    not this exact problem.
    Any ideas would truly be appreciated!
    More information:...
    App and Web server are both wls 6.1.1.0 running on the same SUN Solaris box.
    Both are using the basic, out of the box, security.
    The App server has SSL disabled.
    The exception reported in the app server's log is:
    java.lang.SecurityException: Authentication for user system denied in realm
    wl_realm
    at weblogic.security.acl.Realm.authenticate(Realm.java:212)
    at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
    at
    weblogic.security.acl.internal.Security.authenticate(Security.java:125)
    at weblogic.security.acl.internal.Security.verify(Security.java:87)
    at
    weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:235)
    at
    weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
    2)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    The exception reported in the web server's log is:
    java.lang.SecurityException: Authentication for user system denied in realm
    wl_realm
    at
    weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.
    java:85)
    at
    weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
    :255)
    at
    weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
    :222)
    at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
    at $Proxy54.lookup(Unknown Source)
    at
    weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:323)
    at javax.naming.InitialContext.lookup(InitialContext.java:350)
    at
    com.qwest.tmmt.manager.client.MDMAdapter.getEJBHome(MDMAdapter.java:197)
    at
    com.qwest.tmmt.manager.client.MDMAdapter.<init>(MDMAdapter.java:64)
    at
    com.qwest.tmmt.manager.client.ManagerFactory.createMetaDataManager(ManagerFa
    ctory.java:305)
    at
    com.qwest.insite.util.ClientMetaDataCache.<init>(ClientMetaDataCache.java:53
    at
    com.qwest.insite.util.ClientMetaDataCache.getInstance(ClientMetaDataCache.ja
    va:106)
    at
    com.qwest.insite.metadata.startup.MetaDataServlet.init(MetaDataServlet.java:
    30)
    at
    weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java
    :700)
    at
    weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.ja
    va:643)
    at
    weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.jav
    a:588)
    at
    weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletC
    ontext.java:2203)
    at
    weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServlet
    Context.java:2147)
    at
    weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.jav
    a:884)
    at
    weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.j
    ava:807)
    at
    weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:421)
    at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:74)
    at weblogic.j2ee.Application.addComponent(Application.java:160)
    at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
    arget.java:329)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
    arget.java:144)
    at
    weblogic.management.mbeans.custom.WebServer.addWebDeployment(WebServer.java:
    76)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
    .java:608)
    at
    weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
    92)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
    nImpl.java:352)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
    at $Proxy33.addWebDeployment(Unknown Source)
    at
    weblogic.management.configuration.WebServerMBean_CachingStub.addWebDeploymen
    t(WebServerMBean_CachingStub.java:1094)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
    arget.java:315)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
    Target.java:279)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
    eploymentTarget.java:233)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
    entTarget.java:193)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
    .java:608)
    at
    weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
    92)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
    nImpl.java:352)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
    at $Proxy32.updateDeployments(Unknown Source)
    at
    weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(
    ServerMBean_CachingStub.java:2734)
    at
    weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Appl
    icationManager.java:362)
    at
    weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManage
    r.java:154)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
    .java:608)
    at
    weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
    92)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
    nImpl.java:352)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
    at $Proxy45.start(Unknown Source)
    at
    weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(
    ApplicationManagerMBean_CachingStub.java:480)
    at
    weblogic.management.Admin.startApplicationManager(Admin.java:1151)
    at weblogic.management.Admin.finish(Admin.java:570)
    at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:506)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
    at weblogic.Server.main(Server.java:35)
    Thanks,
    Jed Zimmer

    You're correct. I meant the DOMAIN_SYSTEM_PASSWORD password in my
    <domain-name>domain.ksh file. The DOMAIN_SYSTEM_PASSWORD value (if
    specified) has to match the system user's password or else the server will
    not start/stop.
    I have determined more since my post. A startup class also produces the
    same error. I have minimized my environments as follows and still receive
    the exception, and a soon as I synchronize the system users' passwords on
    the app/web server the problem goes away. Or, I can keep the passwords
    different and just not access the app server EJBs until after the web server
    finished loading, which also causes the error to go away. I'm just confused
    about what I might be doing wrong.
    Steps to produce the error:
    App server:
    - Installed from 6.1.1.0 from scratch and started it up.
    - Changed the system user's password from the admin console, persisting the
    changes.
    - Modified logging settings to see more info in the log files.
    - Disabled instrument stack traces.
    - Stopped/Started the app server
    Web server:
    - Installed from 6.1.1.0 from scratch and started it up.
    - Modified logging settings to see more info in the log files.
    - Disabled instrument stack traces.
    - Added a servlet to the DefaultWebApp_insiteserver application
    - specified name and class
    - the load on startup setting defaulted to zero, which will cause the
    preloading
    - Added 3 jar files to the classpath to support the EJB call
    - Stopped/Started the web server
    When the web server loads the servlet loads and tries to locate the EJB on
    the app server. The app server throws the security exception. The app/web
    servers are both running on the same SUN box, have the same IP address
    (different ports) and I'm using non-SSL. Each server is it's own WLS
    environment. The only installed file that is shared it the
    weblogic_domain_registry.dat file in the root directory. As for security,
    I'm doing nothing except changing one password (system user on the app
    server).
    I then tried to manually upgrade the app/web servers to 6.1.2.0 by updating
    the WEBLOGIC_ROOT in the respective xxxxdomain.ksh files. Same problem.
    I then cleanly reinstalled the app/web servers using version 6.1.2.0 and
    configured as above. Same problem.
    Let me know if I need to provide additional details.
    Thanks,
    Jed Zimmer
    "Joseph Nguyen" <[email protected]> wrote in message
    news:[email protected]...
    >
    "Jed Zimmer" <[email protected]> wrote in message
    news:[email protected]...
    I am experiencing this error when a servlet or JSP is preloaded on the
    web
    server and the init method of the preloaded item results in a call tothe
    app server. If I don't preload and then manually invoke the JSP orservlet
    after the web server completely loads the call to the app server does
    not
    produce the exception. The only security differences between the weband
    app servers are the console and system passwords. I can fix the problemby
    making the passwords (system and console) the same across the board, but
    find it hard to believe that this is the true solutionI don't quite understand what you mean by "console" password? Are you
    talking about the admin console? If so then it's confusing because youhave
    to log into the console using the system user. If you can clarify morehere
    it would great.
    Joseph Nguyen
    BEA Support
    . I would prefer
    sticking with the default security settings.
    I've poured through hundreds of messages. I can find similar problems
    but
    not this exact problem.
    Any ideas would truly be appreciated!
    More information:...
    App and Web server are both wls 6.1.1.0 running on the same SUN Solarisbox.
    Both are using the basic, out of the box, security.
    The App server has SSL disabled.
    The exception reported in the app server's log is:
    java.lang.SecurityException: Authentication for user system denied inrealm
    wl_realm
    at weblogic.security.acl.Realm.authenticate(Realm.java:212)
    atweblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
    at
    weblogic.security.acl.internal.Security.authenticate(Security.java:125)
    atweblogic.security.acl.internal.Security.verify(Security.java:87)
    at
    weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:235)
    at
    weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
    2)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    The exception reported in the web server's log is:
    java.lang.SecurityException: Authentication for user system denied inrealm
    wl_realm
    at
    weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.
    java:85)
    at
    weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
    :255)
    at
    weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
    :222)
    at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
    at $Proxy54.lookup(Unknown Source)
    at
    weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:323)
    at javax.naming.InitialContext.lookup(InitialContext.java:350)
    at
    com.qwest.tmmt.manager.client.MDMAdapter.getEJBHome(MDMAdapter.java:197)
    at
    com.qwest.tmmt.manager.client.MDMAdapter.<init>(MDMAdapter.java:64)
    at
    com.qwest.tmmt.manager.client.ManagerFactory.createMetaDataManager(ManagerFa
    ctory.java:305)
    at
    com.qwest.insite.util.ClientMetaDataCache.<init>(ClientMetaDataCache.java:53
    at
    com.qwest.insite.util.ClientMetaDataCache.getInstance(ClientMetaDataCache.ja
    va:106)
    at
    com.qwest.insite.metadata.startup.MetaDataServlet.init(MetaDataServlet.java:
    30)
    at
    weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java
    :700)
    at
    weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.ja
    va:643)
    at
    weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.jav
    a:588)
    at
    weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletC
    ontext.java:2203)
    at
    weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServlet
    Context.java:2147)
    at
    weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.jav
    a:884)
    at
    weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.j
    ava:807)
    at
    weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:421)
    at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:74)
    at weblogic.j2ee.Application.addComponent(Application.java:160)
    at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
    arget.java:329)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
    arget.java:144)
    at
    weblogic.management.mbeans.custom.WebServer.addWebDeployment(WebServer.java:
    76)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
    .java:608)
    at
    weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
    92)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
    nImpl.java:352)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
    at $Proxy33.addWebDeployment(Unknown Source)
    at
    weblogic.management.configuration.WebServerMBean_CachingStub.addWebDeploymen
    t(WebServerMBean_CachingStub.java:1094)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
    arget.java:315)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
    Target.java:279)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
    eploymentTarget.java:233)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
    entTarget.java:193)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
    .java:608)
    at
    weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
    92)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
    nImpl.java:352)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
    at $Proxy32.updateDeployments(Unknown Source)
    at
    weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(
    ServerMBean_CachingStub.java:2734)
    at
    weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Appl
    icationManager.java:362)
    at
    weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManage
    r.java:154)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
    .java:608)
    at
    weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
    92)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
    nImpl.java:352)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
    at $Proxy45.start(Unknown Source)
    at
    weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(
    ApplicationManagerMBean_CachingStub.java:480)
    at
    weblogic.management.Admin.startApplicationManager(Admin.java:1151)
    at weblogic.management.Admin.finish(Admin.java:570)
    at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:506)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
    at weblogic.Server.main(Server.java:35)
    Thanks,
    Jed Zimmer

  • Javax.naming.AuthenticationException.  Root exception is java.lang.SecurityException: Authentication for user system denied in realm weblogic

    We have started getting the above error message in a system that has worked happily
    for the past 6 months or so (and continues to work happily from our disaster recovery
    environment). I should probably add that this occurs when we are attempting to
    write to the database via the connection pool.
    Anyone have any ideas?
    Thanks
    Andrew
    The full stack trace is
    javax.naming.AuthenticationException. Root exception is java.lang.SecurityException:
    Authentication for user system denied in realm weblogic
         <<no stack trace available>>
    31-Jan-02 00:04:41 GMT Warning Adapter RuntimeException
    thrown by rmi server(class com.esure.ibis.a
    ccesslayer.sb.useraccess.UserAccessBeanEOImpl)
    [265127279722
    6064825S:hfxesure17:[7005,7005,7002,7002,7005,7002,-1]:esure
    prdwls/296]: [BaseEJBObject]
    home: com.esure.ibis.accesslaye
    r.sb.useraccess.UserAccessBeanHomeImpl@4b741e
    com.esure.ibis.util.IbisException: NamingException occurred in UserAccess Session
    Bean::validateUser()
         at com.esure.ibis.accesslayer.sb.useraccess.UserAccessBean.validateUser(UserAccessBean.java:192)
         at com.esure.ibis.accesslayer.sb.useraccess.UserAccessBeanImpl.validateUser(UserAccessBeanImpl.java:110)
         at com.esure.ibis.accesslayer.sb.useraccess.UserAccessBeanEOImpl.validateUser(UserAccessBeanEOImpl.java:31)
         at com.esure.ibis.accesslayer.sb.useraccess.UserAccessBeanEOImpl_WLSkel.invoke(UserAccessBeanEOImpl_WLSkel.java:202)
         at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:373)
         at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:128)
         at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:237)
         at weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestHandler.java:118)
         at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:17)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

    We have started getting the above error message in a system that has worked happily
    for the past 6 months or so (and continues to work happily from our disaster recovery
    environment). I should probably add that this occurs when we are attempting to
    write to the database via the connection pool.
    Anyone have any ideas?
    Thanks
    Andrew
    The full stack trace is
    javax.naming.AuthenticationException. Root exception is java.lang.SecurityException:
    Authentication for user system denied in realm weblogic
         <<no stack trace available>>
    31-Jan-02 00:04:41 GMT Warning Adapter RuntimeException
    thrown by rmi server(class com.esure.ibis.a
    ccesslayer.sb.useraccess.UserAccessBeanEOImpl)
    [265127279722
    6064825S:hfxesure17:[7005,7005,7002,7002,7005,7002,-1]:esure
    prdwls/296]: [BaseEJBObject]
    home: com.esure.ibis.accesslaye
    r.sb.useraccess.UserAccessBeanHomeImpl@4b741e
    com.esure.ibis.util.IbisException: NamingException occurred in UserAccess Session
    Bean::validateUser()
         at com.esure.ibis.accesslayer.sb.useraccess.UserAccessBean.validateUser(UserAccessBean.java:192)
         at com.esure.ibis.accesslayer.sb.useraccess.UserAccessBeanImpl.validateUser(UserAccessBeanImpl.java:110)
         at com.esure.ibis.accesslayer.sb.useraccess.UserAccessBeanEOImpl.validateUser(UserAccessBeanEOImpl.java:31)
         at com.esure.ibis.accesslayer.sb.useraccess.UserAccessBeanEOImpl_WLSkel.invoke(UserAccessBeanEOImpl_WLSkel.java:202)
         at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:373)
         at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:128)
         at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:237)
         at weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestHandler.java:118)
         at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:17)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

  • User Authentication in Web Dynpro Java

    Hi guys,
    I was just wondering how user authentication can be achieved in WDJ? In Web Dynpro ABAP this comes for free when you launch an application. However, in WDJ we can deploy and call the URL without any authentication at all. Is there a way to configure this or do we really have to code this? Thanks! Generous points will be awarded!

    Hi Alex,
    check this links,
    Re: User Authentication in Web Dynpro Application
    Authentication of Web Dynpro
    Using Web Dynpro authentication for a Web Service call
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/dd48d990-0201-0010-92a3-c3ed7e9fd244
    http://help.sap.com/saphelp_nw04s/helpdata/en/04/ee8b8b0d23b746854897adc5611c1d/frameset.htm
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/8304e990-0201-0010-ed8b-d978f1e67b1e
    Regards,
    vino

  • Setup Java system directory server 6 client for user authentication

    I am trying to set up a native LDAP client for sun directory server 6 for network based user authentication. I checked the sun doc for naming service (LDAP) and the documentation are for setting up LDAP client for directory server 5. Is there any documentation for setting up LDAP client for directory server 6? Or the documents for setting LDAP client for directory server 5 is still good for 6? Particularly, I want to use SSL communication between server and client.

    Hi,
    could be one of the other 'bad jokes' of DS/ldapclient because the documentation describes a lot of stuff about profiles etc. but: you need some special schema files to use the whole stuff and they are not installed with Solaris or DS (and they include the NisDomainObject). I had to search for them in the internet. They are also printed in the documentation. Save them in your server's config/schema directory as i.e. 61DUAConfigProfile.ldif and 62nisDomain.ldif and try idsconf again (maybe you have to cleanup something).
    I test and prepare DS6 here, and we will use it in production too. I hadn't any problem with it and it has some important advantages over DS5.2. But we won't have a huge directory so I can't tell you anything more about it.
    Regards
    Jochem Ippers
    Here are the ldifs:
    61DUAConfigProfile.ldif:
    dn: cn=schema
    attributeTypes: ( 1.3.6.1.4.1.11.1.3.1.1.0 NAME 'defaultServerList' DESC 'Default LDAP server host address used by a DUA' EQUALITY caseIgnoreMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 SINGLE-VALUE X-ORIGIN 'user defined' )
    attributeTypes: ( 1.3.6.1.4.1.11.1.3.1.1.1 NAME 'defaultSearchBase' DESC 'Default LDAP base DN used by a DUA' EQUALITY distinguishedNameMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 SINGLE-VALUE X-ORIGIN 'user defined' )
    attributeTypes: ( 1.3.6.1.4.1.11.1.3.1.1.2 NAME 'preferredServerList' DESC 'Preferred LDAP server host addresses to be used by a DUA' EQUALITY caseIgnoreMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 SINGLE-VALUE X-ORIGIN 'user defined' )
    attributeTypes: ( 1.3.6.1.4.1.11.1.3.1.1.3 NAME 'searchTimeLimit' DESC 'Maximum time in seconds a DUA should allow for a search to complete' EQUALITY integerMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 SINGLE-VALUE X-ORIGIN 'user defined' )
    attributeTypes: ( 1.3.6.1.4.1.11.1.3.1.1.4 NAME 'bindTimeLimit' DESC 'Maximum time in seconds a DUA should allow for the bind operation to complete' EQUALITY integerMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 SINGLE-VALUE X-ORIGIN 'user defined' )
    attributeTypes: ( 1.3.6.1.4.1.11.1.3.1.1.5 NAME 'followReferrals' DESC 'Tells DUA if it should follow referrals returned by a DSA search result' EQUALITY caseIgnoreIA5Match SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 SINGLE-VALUE X-ORIGIN 'user defined' )
    attributeTypes: ( 1.3.6.1.4.1.11.1.3.1.1.6 NAME 'authenticationMethod' DESC 'A keystring which identifies the type of authentication method used to contact the DSA' EQUALITY caseIgnoreMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 SINGLE-VALUE X-ORIGIN 'user defined' )
    attributeTypes: ( 1.3.6.1.4.1.11.1.3.1.1.7 NAME 'profileTTL' DESC 'Time to live, in seconds, before a client DUA should re-read this configuration profile' EQUALITY integerMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 SINGLE-VALUE X-ORIGIN 'user defined' )
    attributeTypes: ( 1.3.6.1.4.1.11.1.3.1.1.14 NAME 'serviceSearchDescriptor' DESC 'LDAP search descriptor list used by a DUA' EQUALITY caseExactMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 X-ORIGIN 'user defined' )
    attributeTypes: ( 1.3.6.1.4.1.11.1.3.1.1.9 NAME 'attributeMap' DESC 'Attribute mappings used by a DUA' EQUALITY caseIgnoreIA5Match SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 X-ORIGIN 'user defined' )
    attributeTypes: ( 1.3.6.1.4.1.11.1.3.1.1.10 NAME 'credentialLevel' DESC 'Identifies type of credentials a DUA should use when binding to the LDAP server' EQUALITY caseIgnoreIA5Match SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 SINGLE-VALUE X-ORIGIN 'user defined' )
    attributeTypes: ( 1.3.6.1.4.1.11.1.3.1.1.11 NAME 'objectclassMap' DESC 'Objectclass mappings used by a DUA' EQUALITY caseIgnoreIA5Match SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 X-ORIGIN 'user defined' )
    attributeTypes: ( 1.3.6.1.4.1.11.1.3.1.1.12 NAME 'defaultSearchScope' DESC 'Default search scope used by a DUA' EQUALITY caseIgnoreIA5Match SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 SINGLE-VALUE X-ORIGIN 'user defined' )
    attributeTypes: ( 1.3.6.1.4.1.11.1.3.1.1.13 NAME 'serviceCredentialLevel' DESC 'Identifies type of credentials a DUA should use when binding to the LDAP server for a specific service' EQUALITY caseIgnoreIA5Match SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 X-ORIGIN 'user defined' )
    attributeTypes: ( 1.3.6.1.4.1.11.1.3.1.1.15 NAME 'serviceAuthenticationMethod' DESC 'Authentication method used by a service of the DUA' EQUALITY caseIgnoreMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 X-ORIGIN 'user defined' )
    objectClasses: ( 1.3.6.1.4.1.11.1.3.1.2.4 NAME 'DUAConfigProfile' SUP top STRUCTURAL DESC 'Abstraction of a base configuration for a DUA' MUST ( cn ) MAY ( defaultServerList $ preferredServerList $ defaultSearchBase $ defaultSearchScope $ searchTimeLimit $ bindTimeLimit $ credentialLevel $ authenticationMethod $ followReferrals $ serviceSearchDescriptor $ serviceCredentialLevel $ serviceAuthenticationMethod $ objectclassMap $ attributeMap $ profileTTL ) X-ORIGIN 'user defined' )
    62nisDomain.ldif:
    dn: cn=schema
    attributeTypes: ( 1.3.6.1.1.1.1.30 NAME 'nisDomain' DESC 'NIS domain' SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 X-ORIGIN 'user defined' )
    objectClasses: ( 1.3.6.1.1.1.2.15 NAME 'nisDomainObject' SUP top STRUCTURAL MUST nisDomain X-ORIGIN 'user defined' )

  • Java Iview Runtime error after logon

    Hello,
    we are facing some problem regarding our EP 7.0 SP13. We have an anonymous page as our home page, with some anonymous ivews, like "help", "news", etc and one iview with authentication set to default where users log into the portal and access to the private section of the portal.
    That ivew does a redirection to /irj/portal and since the user is athenticated it will led him to the private home. The problem is that after logon, a Java iview runtime error appears, and users must refresh the browser to access the private section. (user is logged before the error appears).
    We have checked this is not happening with users with "super admin" o "content admin" role. They are able to log into the portal, and redirection is working fine. So we think there can be some problem with security zones or authentication somewhere in the portal, but since this is the standard logon component i don´t know why is this not working.
    We have checked that the redirection is working, and we have made some tests with different kind of iviews like KM iviews, URL iviews, pictures, etc. Only admin users are able to log in correctly, the others get the java iview runtime error, so we think the problem is with to standard logon...
    Here goes a trace of our problem (defaultrace.trc):
    #1.5 #000802B3F434005C00000434000024680004646E64997E00#1236325203820#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in connection#
    #1.5 #000802B3F434005C00000435000024680004646E64998C55#1236325203820#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:304)#
    #1.5 #000802B3F434005C00000436000024680004646E64998E05#1236325203820#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)#
    #1.5 #000802B3F434005C00000437000024680004646E6499900A#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at java.security.AccessController.doPrivileged(Native Method)#
    #1.5 #000802B3F434005C00000438000024680004646E64999183#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)#
    #1.5 #000802B3F434005C00000439000024680004646E649992D1#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#
    #1.5 #000802B3F434005C0000043A000024680004646E6499941A#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)#
    #1.5 #000802B3F434005C0000043B000024680004646E6499955B#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#
    #1.5 #000802B3F434005C0000043C000024680004646E64999690#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)#
    #1.5 #000802B3F434005C0000043D000024680004646E6499984F#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)#
    #1.5 #000802B3F434005C0000043E000024680004646E6499999C#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)#
    #1.5 #000802B3F434005C0000043F000024680004646E64999AEB#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)#
    #1.5 #000802B3F434005C00000440000024680004646E64999C2F#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)#
    #1.5 #000802B3F434005C00000441000024680004646E64999D76#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)#
    #1.5 #000802B3F434005C00000442000024680004646E64999EDA#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)#
    #1.5 #000802B3F434005C00000443000024680004646E6499A01D#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)#
    #1.5 #000802B3F434005C00000444000024680004646E6499A15E#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)#
    #1.5 #000802B3F434005C00000445000024680004646E6499A30A#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)#
    #1.5 #000802B3F434005C00000446000024680004646E6499A479#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)#
    #1.5 #000802B3F434005C00000447000024680004646E6499A5B7#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at java.security.AccessController.doPrivileged(Native Method)#
    #1.5 #000802B3F434005C00000448000024680004646E6499A718#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)#
    #1.5 #000802B3F434005C00000449000024680004646E6499A855#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)#
    #1.5 #000802B3F434005C0000044A000024680004646E6499B6CC#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: PortalRuntimeException#
    #1.5 #000802B3F434005C0000044B000024680004646E6499B86B#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:284)#
    #1.5 #000802B3F434005C0000044C000024680004646E6499BA7E#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     ... 20 more#
    #1.5 #000802B3F434005C0000044D000024680004646E6499CB8B#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###Caused by: com.sapportals.portal.prt.core.PortalRequestManagerException: PortalRuntimeException#
    #1.5 #000802B3F434005C0000044E000024680004646E6499CD54#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:143)#
    #1.5 #000802B3F434005C0000044F000024680004646E6499CE9B#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)#
    #1.5 #000802B3F434005C00000450000024680004646E6499CFDD#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)#
    #1.5 #000802B3F434005C00000451000024680004646E6499D130#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.connection.ContentExceptionHandler.handleException(ContentExceptionHandler.java:100)#
    #1.5 #000802B3F434005C00000452000024680004646E6499D277#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.connection.ContentExceptionHandler.handlePortalRuntimeException(ContentExceptionHandler.java:27)#
    #1.5 #000802B3F434005C00000453000024680004646E6499D512#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalRequestManager.handleRequestException(PortalRequestManager.java:917)#
    #1.5 #000802B3F434005C00000454000024680004646E6499D677#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:803)#
    #1.5 #000802B3F434005C00000455000024680004646E6499D7F3#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)#
    #1.5 #000802B3F434005C00000456000024680004646E6499D943#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     ... 20 more#
    #1.5 #000802B3F434005C00000457000024680004646E6499EB58#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###Caused by: java.lang.UnsupportedOperationException: this implementation does not support getComponentContext()#
    #1.5 #000802B3F434005C00000458000024680004646E6499ECFD#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.service.hook.RedirectNode.getComponentContext(RedirectNode.java:50)#
    #1.5 #000802B3F434005C00000459000024680004646E6499EE40#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:343)#
    #1.5 #000802B3F434005C0000045A000024680004646E6499EF97#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:238)#
    #1.5 #000802B3F434005C0000045B000024680004646E6499F0E1#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)#
    #1.5 #000802B3F434005C0000045C000024680004646E6499F21D#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     ... 27 more#
    can anyone help us with this problem?
    Thanks in advance

    The problem was solved, it was a permission problem.
    The anonymous role which allow access to the anonymous section of the portal was assigned to anonymous user, but it hasn´t everyone permission. So anonymous users were able to see anonymous pages, but when they login they lose the role, and java iview error happened, unless they had admin rights.
    Solved assigned by assigning everyone to that role.
    Thanks

  • Portal Java Iview Runtime - Urgentt

    dear All Portalers,
    we got high issues when SAP ESS/MSS Implementatin for our customer, we got issue about HTTP Session maximum and cause error message "Java Iview Runtime .."
    first, this is our landscape
    1. We Have SAP EP 7 installed with UME integrated with LDAP (Ms. Exchange 2003)
    2. We use SAP ECC 6 SR3 as our Backend System
    3. We use ALL SSL Commnunication between Portal and Backend
    4. We use SPNEGO for User Authentication Mechanism, so User Join Domain, directly open portal when run Internet Explorer between input User and password
    5. Each Uses LDAP mapped use User Mapping
    But, after we launch to customer, we got big problem about Session
    Here, reproduce the error
    1. User Join to Network Domain ( e.g. CORP.CO.ID)
    2. After User/laptop join Network Domain and open browser https://portal.CORP.co.id/
    3. Directly, User logon automatically at Home of SAP ESS/MSS
    4. User finish transaction at SAP Portal and want to Out from Portal by Log off, but after Log off automatically back to entry ( is is Normal ??? )
    5. User very annoying, so user close browser
    6. After 10 seconds, user Open Browser again, open browser https://portal.CORP.co.id/ but user got this message
        "Java Iview Runtime...bla bla bla"
    can any help us , i already set OSS Message Very High ... but didn't solve this problem
    thanks
    regards
    ghochi

    Hi Ghochi,
    First if you want user not to directly log in to Portal then disable the automatic logon setting frominternet explorer.
    Tools > Internet Options > Advance > Enable internet Authentication (uncheck checkbox) restart browser. Next time user will not directly login to Portal. But user needs to enter user ID/PWD every time.
    Coming to your problem for http sessions,
    1. On click of log off button, sessions are not getting released. Please check what is the value once user clicks on log off button. This you can check in Visual admin.
    2. Also, go to SM04 in ECC and check how many http sessions you are having.
    Thanks.
    Sushil

  • User Authentication failed

    Hi all,
    I like to share one of my peculiar issue with you and like to get a solution as well.
    I am trying to install a portal server with r3load based method. I did a java export of mssql Portal server and suceefully imported in the newly installed server.The server is up and running.I also completed the post installation activites like SLD ,SSO and Jco creation. I am not able to log in to the java page using administrator user and also other users..It keep on saying that user authentication is failed.
    But the beauty is that using the same adminsitrator user i am logging in the visaul administrator .
    I dont know where the problem and also i verified the log files under cluset/server nodes. There i found the log as  follows  --- > Connection is already closed and no longer associated with a managed connection,,
    I dont know where i am missing. Due to this I reinstalled the server and imported again..But the same problem is existing to me. Anyone have suggestion on this please do reply.
    Thanks and Regards
    Vijay

    Hi,
    Thnaks for reply. Its only a java system ,, So no activity needs to be done in SU01. I checked the table in database..the users are exisitng as well in the table.
    FYI: I am able to log in visaul admin but not in the java pages like
    http://<hostname>:port/
    http://<hostname>:port/irj
    Hope i explained  my problem it in right way
    Regards
    Vijay

  • CE 7.2 NWDS wdp ws client user authentication error

    Hello CE 7.2  experts !
    I am running a CE 7.2 sp 01 env with NWDS. In my landscape I have some webservices running on PI 7.1.
    I am trying to develop a webdynpro webservice client. When run gets user authentication errors.
    I have configured the Service Groups, provider systems, http destinations etc for this webservice.
    After I have successfully build and deployed the wdp app I am getting error on the wdp gui screen like this:
    Exception on execution of web service with WSDL URL 'http://xxxxxxx.lxx.xxxx.xxx:50000/dir/wsdl?p=sa/595aaad7bedb3cf89546e4651ea9954d' with operation 'GetBudgetRequest_out' in interface 'GetBudgetRequest_out'
    And in log trace:
    Invalid Response code (401). Server <http://xxxxxxx.lxx.xxxx.xxx:50000/XISOAPAdapter/MessageServlet?senderParty=&senderService=SLF&receiverParty=&receiverService=&interface=GetBudgetRequest_out&interfaceNamespace=http%3A%2F%2Fsfso.no%2Fagresso%2Fslf> returned message <Unauthorized>. Http proxy info:  none
    [EXCEPTION]
    com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Invalid Response code (401). Server <http://xxxxxxx.lxx.xxxx.xxx:50000/XISOAPAdapter/MessageServlet?senderParty=&senderService=SLF&receiverParty=&receiverService=&interface=GetBudgetRequest_out&interfaceNamespace=http%3A%2F%2Fsfso.no%2Fagresso%2Fslf> returned message <Unauthorized>. Http proxy info:  none
    at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.handleSOAPResponseMessage(SOAPTransportBinding.java:561)
    at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1316)
    at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:952)
    at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:907)
    at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DInterfaceInvokerImpl.invokeOperation(DInterfaceInvokerImpl.java:76)
    at com.sap.tc.webdynpro.model.webservice.model.WSGenericModelClassExecutable.execute(WSGenericModelClassExecutable.java:73)
    at com.sap.tc.webdynpro.model.webservice.gci.WSTypedModelClassExecutable.execute(WSTypedModelClassExecutable.java:49)
    at com.sap.demo.wd_slf_proj.wd.comp.slf_getbalancecomp.SLF_GetBalanceCustom.executeRequest_GetBudgetRequest_Out(SLF_GetBalanceCustom.java:189)
    at com.sap.demo.wd_slf_proj.wd.comp.slf_getbalancecomp.wdp.InternalSLF_GetBalanceCustom.executeRequest_GetBudgetRequest_Out(InternalSLF_GetBalanceCustom.java:153)
    at com.sap.demo.wd_slf_proj.wd.comp.slf_getbalancecomp.SLF_GetBalanceCompView.onActionSendReq(SLF_GetBalanceCompView.java:187)
    at com.sap.demo.wd_slf_proj.wd.comp.slf_getbalancecomp.wdp.InternalSLF_GetBalanceCompView.wdInvokeEventHandler(InternalSLF_GetBalanceCompView.java:165)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:142)
    at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:75)
    at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.doHandleActionEvent(ProcessingEventPhase.java:159)
    at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.execute(ProcessingEventPhase.java:94)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:162)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:110)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:97)
    at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:514)
    at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:55)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1652)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1466)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingStandalone(ApplicationSession.java:884)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessing(ApplicationSession.java:856)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:343)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:315)
    at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
    at com.sap.tc.webdynpro.serverimpl.wdc.DispatcherServlet.doContent(DispatcherServlet.java:76)
    at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:62)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
    at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:400)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:203)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:438)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:427)
    at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:80)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:268)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
    at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
    at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:54)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:447)
    at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:264)
    at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
    at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:315)
    Any help / hits are appreciated.
    Hope to get a prompt solution.
    best regards,
    Ajeet Phadnis

    Hi,
    I hope please upgrade SP01 to SP05.
    Please look at these two forums
    [forum1|Error executing webservice in BPM; and [forum2|Call to sr.esworkplace fails;
    Hope this is help full for u
    Regards
    Vijay

Maybe you are looking for

  • Remote Control and FQDN from admin console

    Hi everyone, I want to validate something with the community. I have an environment with two domain and there is no DNS Suffixes pushed. When looking at the properties of some computers on the second domain, I can validate that the full name of the c

  • How do i transfer music from PC to a mac?

    i just got a mac and i cant figure out how to transfer the music from itunes on my PC to itunes on my mac. i thought i could use my ipod to do this but it says that my ipod is PC-formatted... i dont want to mess anything up, like accidentally delete

  • Error Statements in PL/SQL Code

    Hello Everyone: I have a PL/SQL routine that I need to add "Error Statments" in case something errors when it is ran, the user will know and be able to fix the issue. Below is a copy of what I need to run. It is a one off that this will only be ran o

  • How do I save my iCloud data?

    How can I save my data so as to transfer it to a new ID?

  • Sales Order & Work Flow

    Hi All, I am developing a report that deals with  sales orders pending for approvals and wf information. 1.I need to know the relation ship between VBAK-VBELN and one of the work flow tables. 2. I need to know Work flow ID , person responsible for Sa