August 2011 - esb-issues - Jboss List Archives

[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, 8 months

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, 8 months

2
7
0 / 0

[JBoss JIRA] Created: (JBESB-1934) Message filters configurable at archive/service level

by Martin Vecera (JIRA)

Message filters configurable at archive/service level ----------------------------------------------------- Key: JBESB-1934 URL: https://jira.jboss.org/jira/browse/JBESB-1934 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 Reporter: Martin Vecera It would be great if message filters (described in linked issue) could be configured at least at archive level (service level would be better). Have it configured globally for all the services doesn't have much sense IMHO. -- 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, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-3632) Use ivy to resolve all of the JARs in the project

by Tom Cunningham (JIRA)

Use ivy to resolve all of the JARs in the project ------------------------------------------------- Key: JBESB-3632 URL: https://issues.jboss.org/browse/JBESB-3632 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.10 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.10 CP1 Wherever applicable, try to retrieve any JARs checked into svn from ivy. There may be some exceptions, but I'll try to document any JARs that cannot be moved over (maybe they aren't available publicly, etc). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-3486) RemoteFileSystemFactory should also support ConfigTree

by Joakim Sandstroem (JIRA)

RemoteFileSystemFactory should also support ConfigTree ------------------------------------------------------ Key: JBESB-3486 URL: https://jira.jboss.org/browse/JBESB-3486 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Adapters Affects Versions: 4.9, 4.4 CP4, 4.8, 4.7 CP2, 4.7 CP1, 4.7, 4.6 Reporter: Joakim Sandstroem org.jboss.soa.esb.util.RemoteFileSystemFactory only supports FTPEpr, it should also provide a factory method that takes a ConfigTree - The configuration tree can then contain RemoteFileSystem.PARMS* Provides: 1. cleaner configuration using separate properties 2. support for directories directly under the user home folder (applies to sftp, issue below) Issue: 1. use the original RemoteFileSystemFactory and provide sftp://sftp-user:pwd@sftp.server/test-dir as the ftp epr 2. test-dir resides directly in the sftp-user home directory 3. try to upload a file to this directory -> You get the following exception: Caused by: org.jboss.soa.esb.util.RemoteFileSystemException: 2: No such file at org.jboss.internal.soa.esb.util.SecureFtpImpl.uploadFile(SecureFtpImpl.java:578) at fi.barona.esb.integration.sonet.Sonet.sendFile(Sonet.java:142) ... 14 more Caused by: 2: No such file at com.jcraft.jsch.ChannelSftp.throwStatusError(ChannelSftp.java:2291) at com.jcraft.jsch.ChannelSftp._realpath(ChannelSftp.java:1824) at com.jcraft.jsch.ChannelSftp.cd(ChannelSftp.java:263) at org.jboss.internal.soa.esb.util.SecureFtpImpl.uploadFile(SecureFtpImpl.java:548) ... 15 more The above exception occurs because jsch (sftp) does not recognize that the test-dir resides directly in the user home folder, the path should be test-dir, not /test-dir -- 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, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-2469) Remote directory cannot be relative for (S)FTP(S) gateway

by Martin Vecera (JIRA)

Remote directory cannot be relative for (S)FTP(S) gateway --------------------------------------------------------- Key: JBESB-2469 URL: https://jira.jboss.org/jira/browse/JBESB-2469 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 CP2 Reporter: Martin Vecera FtpImpl, SecureFtpImpl and FtpsImpl are calling "cd" with the directory specified in jboss-esb.xml every time they are getting list of files. When the directory is specified relatively you would need structure like ftp_dir/ftp_dir/ftp_dir/ftp_dir... This must be at least documented, but doing cd every X seconds is waste of time. It should be sufficient only once IMHO. -- 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, 9 months

5
6
0 / 0

[JBoss JIRA] Created: (JBESB-3022) It is not possible to use different credentials on the input of the service and on the SOAPProxy that invokes the proxied service

by Jiri Pechanec (JIRA)

It is not possible to use different credentials on the input of the service and on the SOAPProxy that invokes the proxied service --------------------------------------------------------------------------------------------------------------------------------- Key: JBESB-3022 URL: https://jira.jboss.org/jira/browse/JBESB-3022 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.7 Reporter: Jiri Pechanec Attachments: soapproxy-diffauth.zip There is a use case - I have a secured ESB service using HTTPS/BASIC auth invoking invoking secured HTTPS/BASIC auth web service via SOAPProxy. If the credentials are passed from the client then everything works correctly. But if I have different credentials required for ESB client and different credentials are required by proxied Web Service then I use property <property name="clientCredentialsRequired" value="false" /> to set static credentials for proxied web service. This property works correctly if the ESB service is unsecured. Unfortunately if it is secured then probably the credentials stored in HTTP header stored in ESB message overwrites the static credentials set by the SOAPProxy action. The attached example is modified webservice_proxy_secure QS and has static credentials set to wrong values - so proxied web service should not be invoked. But if ant runtest is executed then the wrong credentials are not used. -- 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, 9 months

5
11
0 / 0

[JBoss JIRA] Created: (JBESB-3641) JSF issues with jbpm-console and AS6

by Tom Cunningham (JIRA)

JSF issues with jbpm-console and AS6 ------------------------------------ Key: JBESB-3641 URL: https://issues.jboss.org/browse/JBESB-3641 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.11 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.11 Investigate / Release note the JSF errors occurring in the jbpm-console on AS6. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-3357) Mavenise the ESB build

by Kevin Conner (JIRA)

Mavenise the ESB build ---------------------- Key: JBESB-3357 URL: https://jira.jboss.org/browse/JBESB-3357 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.8 Reporter: Kevin Conner Priority: Optional Fix For: 4.9 To be done for 4.9 if we have time. -- 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, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-2272) ESB testable against external binaries (product test suite)

by Aleksandar Kostadinov (JIRA)

ESB testable against external binaries (product test suite) ----------------------------------------------------------- Key: JBESB-2272 URL: https://jira.jboss.org/jira/browse/JBESB-2272 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.2.1 CP3, 4.2.1 CP2, 4.2.1 CP1, 4.2.1 CP4 Reporter: Aleksandar Kostadinov When running the ESB test suite against external binaries, there is currently a mismatch between libraries downloaded by the test suite and libraries found in the external distribution. This makes running the suite against the external JBoss AS distribution meaningless because doesn't prove ESB will work with the libraries found in the JBoss AS server. As a solution I see, the various junit tasks run by the testsuite should have classpath point at the libraries in the JBoss AS rather than these generated during build and downloaded by the build script. Running the test suite against external binaries should be the same as verifying an ESB installation (be it on top of JBoss AS or standalone). The issue supersedes JBESB-1513 and is the cause of JBESB-1711. -- 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, 9 months

4
17
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues August 2011