May 2012 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3378) Both JAXWS & JAXRPC handlers have to be executed in EJB interceptor after EJB security interceptors

by Richard Opalka (Created) (JIRA)

Both JAXWS & JAXRPC handlers have to be executed in EJB interceptor after EJB security interceptors --------------------------------------------------------------------------------------------------- Key: JBWS-3378 URL: https://issues.jboss.org/browse/JBWS-3378 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Richard Opalka 6.2.2.4 Security Handlers associated with a Port component run after authorization has occurred and before the business logic method of the Service Implementation bean is dispatched to. For JAX-RPC or JAX-WS Service endpoints, Handlers run after the container has performed the security constraint checks associated with the servlet element that defines the Port component. For EJB based service implementations, Handlers run after method level authorization has occurred. -- 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 months

7
11
0 / 0

[JBoss JIRA] Created: (JBWS-3237) Set an HTTP proxy host/port for an individual WS-stub

by Roger Hui (JIRA)

Set an HTTP proxy host/port for an individual WS-stub ----------------------------------------------------- Key: JBWS-3237 URL: https://issues.jboss.org/browse/JBWS-3237 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.4.1 Environment: EAP 4.3.X and EAP 5.x Reporter: Roger Hui Priority: Minor We would like to set an HTTP proxy host/port for an individual WS-stub. We found [1], but the link goes to a dead page [2], and we found a valid JBoss Remoting page [3]. In [3] it shows that the proxy host/port can be configured in the client metadata. However, we don't see how to set this from JBossWS. We would like this to be a new feature. [1] http://community.jboss.org/wiki/JBossWS-FAQ#How_can_I_setup_my_client_to_... [2] http://labs.jboss.com/jbossremoting/docs/guide/ch05.html [3] http://docs.jboss.org/jbossremoting/docs/guide/2.5/html/index.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
6
0 / 0

[JBoss JIRA] (JBWS-3496) Enable CXF WS-MetadataExchange (Aug 2006 spec) support

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3496: ------------------------------------- Summary: Enable CXF WS-MetadataExchange (Aug 2006 spec) support Key: JBWS-3496 URL: https://issues.jboss.org/browse/JBWS-3496 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.1 Apache CXF 2.5.x comes with WS-MetadataExchange ( http://schemas.xmlsoap.org/ws/2004/09/mex/ ) support. While we're probably going to explore supporting the newer version included in the WS-RA specs, we should start by unlocking the implementation already available from Apache CXF. -- 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 months

1
1
0 / 0

[JBoss JIRA] (JBWS-3500) @SchemaValidation doesn't work in JBoss 7.1.1 Final

by Jim Ma (JIRA)

Jim Ma created JBWS-3500: ---------------------------- Summary: @SchemaValidation doesn't work in JBoss 7.1.1 Final Key: JBWS-3500 URL: https://issues.jboss.org/browse/JBWS-3500 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-cxf-4.1 -- 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, 4 months

4
8
0 / 0

[JBoss JIRA] Created: (JBWS-2932) Support for HTTP Digest authentication, when acting as a client to an external web service

by Ian (JIRA)

Support for HTTP Digest authentication, when acting as a client to an external web service ------------------------------------------------------------------------------------------ Key: JBWS-2932 URL: https://jira.jboss.org/jira/browse/JBWS-2932 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-metro-3.2.1, jbossws-native-3.2.1, jbossws-cxf-3.2.1 Reporter: Ian Please implement HTTP Digest Authentication when acting as a client to an external web service. I don't mean using WS-Security, just using HTTP authentication in a similar that Basic Authentication is used - using JAX-WS code similar to this: String url = configuration.getString(CONFIG_URL); BindingProvider provider = (BindingProvider)requestInvoker; provider.getRequestContext().put(BindingProvider.USERNAME_PROPERTY, username); provider.getRequestContext().put(BindingProvider.PASSWORD_PROPERTY, password); This code works if run as a standalone java client (probably because Metro supports it). However it doesn't work with JBossWS: * Native implementation simply doesn't work at all * Metro implementation has classloading issues when web service calls are made (to do with WS-Addressing I think, I've seen other posts about it). * CXF has the same issues as Metro Given from my reading that the WS-Security work supports Digest authentication, it doesn't seem a difficult task. I'd suggest one of two ways to fix it: 1. Implement it in JBossWS native, OR 2. Fix the classloading issues in Metro and/or CXF so those stacks can be used (given they already support it). -- 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, 4 months

3
3
0 / 0

[JBoss JIRA] Created: (JBWS-2569) Soap over TCP/IP Transport for Jboss WS

by Bryan Kearney (JIRA)

Soap over TCP/IP Transport for Jboss WS --------------------------------------- Key: JBWS-2569 URL: https://jira.jboss.org/jira/browse/JBWS-2569 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Environment: Jboss 5.0.X, any WS stack, running on Fedora Reporter: Bryan Kearney I would like to see one of the supported WS stackes support SOAP over a TCP/IP transport instead of http. I have 2 main drivers for this: 1) Performance (http://blogs.sun.com/oleksiys/entry/soap_tcp_makes_web_services). 2) Interoperability with the M$ stack, specifically the WCF classes. -- bk -- 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, 4 months

3
4
0 / 0

[JBoss JIRA] Created: (JBWS-3335) Evaluate adding client-configuration to AS7 domain model

by Alessio Soldano (JIRA)

Evaluate adding client-configuration to AS7 domain model -------------------------------------------------------- Key: JBWS-3335 URL: https://issues.jboss.org/browse/JBWS-3335 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration, jbossws-native Reporter: Alessio Soldano Fix For: jbossws-native-4.0, jbossws-cxf-4.0 In JBWS-3286 we added endpoint configurations to the AS7 domain. We need to evaluate the feasibility of doing the same for jaxws client configurations. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

2
7
0 / 0

[JBoss JIRA] Created: (JBWS-1814) Dynamic Encryption based on clients input

by Magesh Kumar B (JIRA)

Dynamic Encryption based on clients input ----------------------------------------- Key: JBWS-1814 URL: http://jira.jboss.com/jira/browse/JBWS-1814 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ws-security Affects Versions: jbossws-2.0.1, jbossws-1.2.1 Reporter: Magesh Kumar B Let's say that Bob runs the web service and Alice has a client that uses the web service. Now John would also like to use the web service. John would create: johns.keystore ---------------- john - keyPair (pub+priv) bob - trustedCertEntry (pub) johns.truststore ---------------- john - trustedCertEntry (just john's public key) In addition, Bob's keystore would be updated to: bobs.keystore ---------------- bob - keyPair (public + private key) alice - trustedCertEntry (just alice's public key) john - trustedCertEntry (just john's public key) This does not pose a problem for encrypting the request from the client side since both Alice and John use Bob's public key to encrypt the message, and Bob of course uses his pirvate key to decrypt the message. But how is the response message encrypted? JBossWS apparently does not support multiple clients because the certificate used by the server to encrypt the response is specified statically in jboss-wsse-server.xml. -- 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, 5 months

4
4
0 / 0

[JBoss JIRA] (JBWS-3461) HTTPS / TLS Client certificate authentication does not give client certificate to server side

by Tomas Gustavsson (JIRA)

Tomas Gustavsson created JBWS-3461: -------------------------------------- Summary: HTTPS / TLS Client certificate authentication does not give client certificate to server side Key: JBWS-3461 URL: https://issues.jboss.org/browse/JBWS-3461 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Environment: JBoss AS 7.1.0.GA Reporter: Tomas Gustavsson We use client certificate authentication (TLS) for our webservice (JAX-WS annotated EJB). In JBoss 5 and 6 the following code worked to fetch the client certificate in the session bean. MessageContext msgContext = wsContext.getMessageContext(); HttpServletRequest request = (HttpServletRequest) msgContext.get(MessageContext.SERVLET_REQUEST); X509Certificate[] certificates = (X509Certificate[]) request.getAttribute("javax.servlet.request.X509Certificate"); In JBoss AS 7.1.0.GA no certificate is retrieved. -- 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, 5 months

3
5
0 / 0

[JBoss JIRA] (JBWS-3446) Evaluate options for enabling username over transport security wsse tests

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3446: ------------------------------------- Summary: Evaluate options for enabling username over transport security wsse tests Key: JBWS-3446 URL: https://issues.jboss.org/browse/JBWS-3446 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Fix For: jbossws-cxf-4.1 <ropalka> asoldano, IMHO we should remove <ropalka>  <ropalka> <exclude>org/jboss/test/ws/jaxws/samples/wssePolicy/UsernameTestCase.*</exclude> <ropalka> <exclude>org/jboss/test/ws/jaxws/samples/wsse/policy/basic/UsernameOverTransportTestCase.*</exclude> <ropalka> asoldano, from our test suite. Because having tests that are not executed doesn't make sense 2 me <ropalka> asoldano, WDYT? <asoldano> ropalka, I don't agree because tests are also needed as examples / tutorials to users <asoldano> ropalka, so if they want to see how to do that, they need those tests <asoldano> ropalka, this said, we should actually try them from time to time... <ropalka> asoldano, ok <ropalka> asoldano, shouldn't be these tests part of jboss quickstart ? <asoldano> ropalka, maybe.. <asoldano> ropalka, do you know btw if the AS7 testsuite has SSL tests? <asoldano> ropalka, we might copy/extend them to cover our wsse transport security tests above <ropalka> asoldano, I have no idea. Ask Darran or Anil <ropalka> asoldano, that would be great <darran> asoldano, it is not something I have worked on myself but I think I have seen some in there <asoldano> darran, interesting, thanks -- 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, 5 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues May 2012