March 2012 - esb-issues - Jboss List Archives

[JBoss JIRA] (JBESB-3737) Syntax error in opensso quickstart readme

by Tom Cunningham (JIRA)

Tom Cunningham created JBESB-3737: ------------------------------------- Summary: Syntax error in opensso quickstart readme Key: JBESB-3737 URL: https://issues.jboss.org/browse/JBESB-3737 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.11 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.11 The read instructs the user to alter the Tomcat catalina.sh file to look like this: After Editing: JAVA_OPTS="$JAVA_OPTS -Xmx1G -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager" But, the (full) line should read: JAVA_OPTS="$JAVA_OPTS -Xmx1G -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.util.logging.config.file=$CATALINA_BASE/conf/logging.properties " -- 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

2
3
0 / 0

[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, 1 month

2
8
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, 1 month

3
4
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 month

1
1
0 / 0

[JBoss JIRA] (JBESB-3761) Create a JBPM 5 BpmProcessor

by Tom Cunningham (JIRA)

Tom Cunningham created JBESB-3761: ------------------------------------- Summary: Create a JBPM 5 BpmProcessor Key: JBESB-3761 URL: https://issues.jboss.org/browse/JBESB-3761 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.11 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.11 Create a JBPM 5 BpmProcessor. -- 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

1
3
0 / 0

[JBoss JIRA] (JBESB-3767) Fix issues with jaas JAR

by Tom Cunningham (JIRA)

Tom Cunningham created JBESB-3767: ------------------------------------- Summary: Fix issues with jaas JAR Key: JBESB-3767 URL: https://issues.jboss.org/browse/JBESB-3767 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.11 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.11 ESB build is choking on a missing jaas JAR after an ivy clean cache. Exclude this from build, and exclude multiple versions of AOP classes. -- 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, 2 months

1
2
0 / 0

[JBoss JIRA] (JBESB-3763) Upgrade jbpm 3 to 3.2.12

by Tom Cunningham (JIRA)

Tom Cunningham created JBESB-3763: ------------------------------------- Summary: Upgrade jbpm 3 to 3.2.12 Key: JBESB-3763 URL: https://issues.jboss.org/browse/JBESB-3763 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.11 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.11 Upgrade jbpm 3 to 3.2.12 -- 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, 2 months

1
2
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, 2 months

5
7
0 / 0

[JBoss JIRA] (JBESB-3771) Use appropriate JAXB jars when installing to AS

by Magesh Bojan (JIRA)

Magesh Bojan created JBESB-3771: ----------------------------------- Summary: Use appropriate JAXB jars when installing to AS Key: JBESB-3771 URL: https://issues.jboss.org/browse/JBESB-3771 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.11 Reporter: Magesh Bojan Assignee: Magesh Bojan Priority: Optional Fix For: 4.11 When installing to AS, use appropriate JAXB implementation jars from the server's client library. This ensures there is no conflict and the compatible version of that server is used. -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] (JBESB-3770) Fix regression in WISE quickstarts

by Magesh Bojan (JIRA)

Magesh Bojan created JBESB-3770: ----------------------------------- Summary: Fix regression in WISE quickstarts Key: JBESB-3770 URL: https://issues.jboss.org/browse/JBESB-3770 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples, Web Services Affects Versions: 4.11 Reporter: Magesh Bojan Assignee: Magesh Bojan Fix For: 4.11 Fix regressions in WISE quickstarts induced due to JBESB-3755, JBESB-3765 and JBESB-3766. -- 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, 2 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues March 2012