July 2012 - jbossws-issues - Jboss List Archives

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

3
4
0 / 0

[JBoss JIRA] (JBWS-3517) Upgrade to Apache CXF 2.7

by Alessio Soldano (JIRA)

12 years, 3 months

2
1
0 / 0

[JBoss JIRA] (JBWS-3530) Add some hints to the code generated by cxf using wsconsume to tune generated code before use

by Mustafa Musaji (JIRA)

Mustafa Musaji created JBWS-3530: ------------------------------------ Summary: Add some hints to the code generated by cxf using wsconsume to tune generated code before use Key: JBWS-3530 URL: https://issues.jboss.org/browse/JBWS-3530 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-4.0.2 Environment: JBossWS CXF Reporter: Mustafa Musaji Assignee: Alessio Soldano Priority: Trivial The generated code when using wsconsume is not really meant for use in production environment with the statically initialized wsdlLocation and the error that will be logged when this the Service object is first initialized. {code:title=WSService.java|borderStyle=solid} static { URL url = null; try { url = new URL("file:/directory/to/wsdl/WSTestEJB/ejbModule/META-INF/WSProvider.wsdl"); } catch (MalformedURLException e) { java.util.logging.Logger.getLogger(WSProviderService.class.getName()) .log(java.util.logging.Level.INFO, "Can not initialize the default wsdl from {0}", "file:/directory/to/wsdl/WSTestEJB/ejbModule/META-INF/WSProvider.wsdl"); } WSDL_LOCATION = url; } {code} This is a request to amend the log level to "DEBUG" and/or have wsconsume create a hint of sorts to tune this class before use in a container. -- 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

1
0
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, 4 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, 4 months

4
4
0 / 0

[JBoss JIRA] (JBWS-3518) static wsdl not recognized

by Daniele Pirola (JIRA)

12 years, 4 months

3
5
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, 4 months

3
5
0 / 0

[JBoss JIRA] (JBWS-3512) Try WS-I Basic Security Profile (BSP) tools

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3512: ------------------------------------- Summary: Try WS-I Basic Security Profile (BSP) tools Key: JBWS-3512 URL: https://issues.jboss.org/browse/JBWS-3512 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, productization Reporter: Alessio Soldano Fix For: jbossws-cxf-4.1 We should try the WS-I BSP tools and try to get an idea of where we are with JBossWS / Apache CXF: http://www.ws-i.org/deliverables/workinggroup.aspx?wg=testingtools -- 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

1
1
0 / 0

[JBoss JIRA] (JBWS-3528) Endpoint metrics do not work

by Mustafa Musaji (JIRA)

Mustafa Musaji created JBWS-3528: ------------------------------------ Summary: Endpoint metrics do not work Key: JBWS-3528 URL: https://issues.jboss.org/browse/JBWS-3528 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-3.1.1 Environment: SLES 10 SP2 with SUN Java SDK 1.5.0_13, JBoss 4.2.3 and JBoss 5.1.0 and jbossws-cxf-3.1.1 Reporter: Mustafa Musaji Assignee: Alessio Soldano Fix For: jbossws-cxf-3.2.0 When we consume an EJB 3 web service deployed at jbossws-cxf-3.1.1, its registered service endpoint metrics counters (RequestCount, ResponseCount... shown at http://127.0.0.1:8080/jbossws/services) not work: never increment values and always show cero. Same happens with a POJO JSR-181 web service endpoint. Its registered service endpoint metrics counters (RequestCount, ResponseCount... shown at http://127.0.0.1:8080/jbossws/services) not work: never increment values and always show cero. But the same web service deployed with jbossws-native, its registered service endpoint metrics counters work fine. -- 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

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 July 2012