++ This bug is a clone of bug 778977 ++ Affects: Documentation (Ref Guide, User Guide, etc.), Interactive Demo/Tutorial, Compatibility/Configuration, Release Notes Date of First Response: 2009-10-23 13:10:43 Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/?module=issues&action=view&tid=313752&gid=1354 project_key: SOA Currently there is no support for supplying jndi security credentials and principals which should be added. I also think that the EJBProcessor could be refactored to be simpler but I'll create a jira for that and link it to this one. In customer case: At source code for EJBProcessor.java: By making adding modifications (line 247) props.put(Context.INITIAL_CONTEXT_FACTORY, ejbRef.get(INICTXFACTORY)); props.put(Context.PROVIDER_URL, ejbRef.get(PROVIDERURL)); props.put(Context.SECURITY_PRINCIPAL, "a username"); props.put(Context.SECURITY_CREDENTIALS, "a password"); and also by using org.jboss.security.jndi.JndiLoginInitialContextFactory now it supports the call of EJB's running in different security contexts and with the required authentication. Regards, Marc
Link: Added: This issue depends JBESB-2695
Already present in ESB trunk.
Verified in ER7.