January 2012 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-3670) Need to review log warnings on AS 6.1

by Tom Cunningham (JIRA)

Need to review log warnings on AS 6.1 ------------------------------------- Key: JBESB-3670 URL: https://issues.jboss.org/browse/JBESB-3670 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment Affects Versions: 4.10 Reporter: Tom Cunningham Assignee: Tom Cunningham Priority: Minor Fix For: 4.10 CP1, 4.11 08:57:44,197 ERROR [STDERR] log4j:WARN No appenders could be found for logger (org.jboss.soa.esb.listeners.deployers.mc.as6.EsbConfigParser). 08:57:44,198 ERROR [STDERR] log4j:WARN Please initialize the log4j system properly. 08:57:44,198 ERROR [STDERR] log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. . . . 08:57:58,495 INFO [Configuration] Reading mappings from resource : META-INF/esb-juddi-orm.xml 08:57:58,513 ERROR [ErrorLogger] Error parsing XML (5) : cvc-complex-type.3.1: Value '1.0' of attribute 'version' of element 'entity-mappings' is not valid with respect to the corresponding attribute use. Attribute 'version' has a fixed value of '2.0'. . . . A lot of these: 08:58:11,127 INFO [org.jboss.soa.esb.listeners.deployers.mc.as6.EsbDeployment] Starting ESB Deployment 'jbpm.esb' 08:58:11,130 WARN [org.hibernate.util.DTDEntityResolver] recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide! -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

2
8
0 / 0

[JBoss JIRA] Created: (JBESB-3626) Upgrade base server

by Tom Cunningham (JIRA)

Upgrade base server -------------------- Key: JBESB-3626 URL: https://issues.jboss.org/browse/JBESB-3626 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.11 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.11 For a long time, the base server has been based off of jboss 4.2.3.GA. Upgrade the base server to something more recent (5.1.0.GA or possibly even AS 7?) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
1
0 / 0

[JBoss JIRA] (JBESB-3723) Add support for WS-Security UsernameToken with digested password, nonces and timestamps.

by Duncan Doyle (Created) (JIRA)

Add support for WS-Security UsernameToken with digested password, nonces and timestamps. ---------------------------------------------------------------------------------------- Key: JBESB-3723 URL: https://issues.jboss.org/browse/JBESB-3723 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Security, Web Services Affects Versions: 4.10 Environment: JBoss SOA-Platform 5.2.0 Reporter: Duncan Doyle Current support for WS-Security UsernameToken in JBoss ESB is limited to usernames and passwords passed in plain text in the WS-Security SOAP header. JBossWS supports UsernameToken with digested passwords, nonces and timestamps. So, an ESB service could be fronted with a JBossWS webservice with UsernameToken with digested password and nonce, which can call the ESB service via ServiceInvoker, or which can be used in an ActionPipeline via SOAPProcessor. However, in that case, the authenticated user (and his roles) will not be propagated through the ESB services as no AuthenticationRequest is set on the ESB message. This has the big disadvantage that the ESB services themselves can not be secured. The attached code shows an implementation which is able to retrieve the username, digested password, nonce and timestamp from within a JAX-WS endpoint. This data is used to create an ESB AuthenticationRequest, where nonce and timestamp are set on the properties map. The new UserDigestPasswordCallbackHandler is based on the UserPassCallbackHandler and is able to retrieve the nonce and timestamp from the AuthenticationRequest and make them availble to the UsernameTokenCallback. This solution provides the ability to propagate the original user and his roles through the entire services chain. It also allows the ESB services to use the same security-domain configuration as the JAX-WS endpoint. I'm aware that the JAX-WS endpoint code might be hard to include in the ESB platform itself, but, if it can not be included in a default component, it might be a nice idea to include this example in one of the quickstarts. The 'application-policy' used in this setup is the setup from the Web Services chapter in the JBoss EAP 5.1 Administration and Configuration Guide: <application-policy name="jbossws-domain"> <authentication> <login-module code="org.jboss.security.auth.spi.UsersRolesLoginModule" flag="required"> <module-option name="usersProperties">props/jbossws-domain-users.properties</module-option> <module-option name="rolesProperties">props/jbossws-domain-roles.properties</module-option> <module-option name="hashAlgorithm">SHA</module-option> <module-option name="hashEncoding">BASE64</module-option> <module-option name="hashUserPassword">false</module-option> <module-option name="hashStorePassword">true</module-option> <module-option name="storeDigestCallback">org.jboss.ws.extensions.security.auth.callback.UsernameTokenCallback</module-option> </login-module> </authentication> </application-policy> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-3657) wsdl url in contract console truncated

by Jaroslaw Kijanowski (JIRA)

wsdl url in contract console truncated -------------------------------------- Key: JBESB-3657 URL: https://issues.jboss.org/browse/JBESB-3657 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Tooling Affects Versions: 4.10 Environment: jbossesb-4.10(a)jboss-5.1.0.GA java version "1.6.0_26" Reporter: Jaroslaw Kijanowski I deploy the webservice_proxy_basic and go to the contract console. The urls is http://127.0.0.1:8080/Quickstart_webservice_proxy_b/http/Proxy_Basic/Prox... instead of http://127.0.0.1:8080/Quickstart_webservice_proxy_basic/http/Proxy_Basic/... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

5
7
0 / 0

[JBoss JIRA] (JBESB-3727) WISE SOAPClient fails to work with WRAPPED services

by Magesh Bojan (JIRA)

Magesh Bojan created JBESB-3727: ----------------------------------- Summary: WISE SOAPClient fails to work with WRAPPED services Key: JBESB-3727 URL: https://issues.jboss.org/browse/JBESB-3727 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.10 Reporter: Magesh Bojan Assignee: Magesh Bojan Fix For: 4.10 CP1 Using WRAPPED services not all parameters are mapped to the SOAP request envelope. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
11
0 / 0

[JBoss JIRA] Created: (JBESB-3461) Reduce classpath

by Kevin Conner (JIRA)

Reduce classpath ---------------- Key: JBESB-3461 URL: https://jira.jboss.org/browse/JBESB-3461 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.9 Reporter: Kevin Conner Fix For: 4.9 CP1 The windows CI runs are failing because of the number of jars being included in their classpath. This may be due to transitive dependencies being pulled in through ivy. We need to look at the list of jars on the classpath and trim accordingly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-3260) Allow preservation of SOAPHeader in ESB Message

by Magesh Kumar B (JIRA)

Allow preservation of SOAPHeader in ESB Message ----------------------------------------------- Key: JBESB-3260 URL: https://jira.jboss.org/jira/browse/JBESB-3260 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.7 CP1 Reporter: Magesh Kumar B Fix For: 4.8 It would be a nice feature to have ESB exposed as WS to have the SOAPHeader elements both ways. -- 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

12 years, 1 month

3
5
0 / 0

[JBoss JIRA] (JBESB-3724) Global Action Pipeline Interceptor

by Brad Davis (Created) (JIRA)

Global Action Pipeline Interceptor ---------------------------------- Key: JBESB-3724 URL: https://issues.jboss.org/browse/JBESB-3724 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.10 Reporter: Brad Davis We would like to have the capability to intercept prior to the action pipeline the Message, globally. This will lay the foundation for being able to hook in global interceptors for global exception handling, business activity monitoring, and service analytics. When the interceptor is executed for the service, it would be helpful to send in not just the Message, but information on the current service (name, etc) as well. This may include which adapter the message is arriving on, what the service name and category is, etc. We have tried in the past to create something like this for a client using AOP, but couldn't achieve it this way, as JBoss AOP has some serious limitations in the Enterprise offerings. It would be also great if the interceptor had the capability to read the full configuration of the service to know what listeners are provided. This could be used in the future to log inputs for services to a service registry. In addition to the hooks for this in the Action Pipeline code, we would also need to have a globally defined configuration for interceptors. The background behind this request is that often times, clients need to do analytics over service request / response times, or need to globally define rules for Exception Handling, or need to intercept input and output messages for auditing. We are hoping that this feature would facilitate all of these by allowing Red Hat to start shipping generic implementations for these things incrementally, and also enabling customers to craft their own to meet specific business needs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

5
9
0 / 0

[JBoss JIRA] Created: (JBESB-2460) BinarySecurityToken class hardwired to X.509 certificates

by Rune Molin (JIRA)

BinarySecurityToken class hardwired to X.509 certificates --------------------------------------------------------- Key: JBESB-2460 URL: https://jira.jboss.org/jira/browse/JBESB-2460 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Security Affects Versions: 4.5 Reporter: Rune Molin In order to support WS Security Kerberos Token Profile at a later time, please make the class org.jboss.soa.esb.services.security.auth.ws.BinarySecurityToken abstract. Currently it is hardwired to only support X.509 Certificate Token Profile. By making this class abstract sooner rather than later, users could implement Kerberos Token Profile themselves, without having to duplicate too much code. This will of course mean moving the existing certificate bound implementation into a new class, CertificateSecurityToken perhaps -- 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

12 years, 1 month

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-1208) BPM & ESB Quickstart for human task management

by Burr Sutter (JIRA)

BPM & ESB Quickstart for human task management ---------------------------------------------- Key: JBESB-1208 URL: http://jira.jboss.com/jira/browse/JBESB-1208 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 IR2 Reporter: Burr Sutter Assigned To: Burr Sutter Priority: Minor Fix For: 4.2.1 bpm_orchestration4 illustrates how to have both ESB service invocation, async bpm signals, business rule services and human task management in a single example. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

2
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues January 2012