[
https://jira.jboss.org/jira/browse/JBESB-2695?page=com.atlassian.jira.plu...
]
Daniel Bevenius updated JBESB-2695:
-----------------------------------
Component/s: Documentation
Going to add an additional property to this action: 'security-login-module'.
If this property is specified it should identify the JAAS login module from
login-config.xml that should be used. The EJBProcessor will then perform a JAAS login.
This will work for containers that support pure JAAS login for ejbs, like AS5.
If you only specify the 'security-principal' and 'security-credentials'
you'll have to specify an initial context factory that accepts
'java.naming.security.principal' and 'java.naming.security.credentials',
like 'org.jboss.security.jndi.JndiLoginInitialContextFactory' for example.
Add jndi security support to EJBProcessor
-----------------------------------------
Key: JBESB-2695
URL:
https://jira.jboss.org/jira/browse/JBESB-2695
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Documentation, Security
Reporter: Daniel Bevenius
Assignee: Daniel Bevenius
Fix For: 4.7
Attachments: EJBProcessor.java, ejbprocessor_with_Login_Credentials.zip,
jbossesb-slsb.jar, login-config.xml, soa-roles.properties, soa-users.properties
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira