September 2012 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2710) Provide testcase for WS-Trust (server side) and WS-SecureConversation

by Alessio Soldano (JIRA)

Provide testcase for WS-Trust (server side) and WS-SecureConversation --------------------------------------------------------------------- Key: JBWS-2710 URL: https://jira.jboss.org/jira/browse/JBWS-2710 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Assignee: Alessio Soldano http://cwiki.apache.org/CXF20DOC/ws-trust.html http://cwiki.apache.org/CXF20DOC/ws-secureconversation.html -- 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

11 years, 7 months

1
4
0 / 0

[JBoss JIRA] (JBWS-3504) Add ability to configure the CXF policy alternative selector on server side

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3504: ------------------------------------- Summary: Add ability to configure the CXF policy alternative selector on server side Key: JBWS-3504 URL: https://issues.jboss.org/browse/JBWS-3504 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 As a consequence of JBWS-3149, JBossWS-CXF defaults to MaximalAlternativeSelector on server side. We need an option for letting users configure a different behavior if they really want to. -- 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

11 years, 7 months

1
2
0 / 0

[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

11 years, 7 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

11 years, 7 months

2
6
0 / 0

[JBoss JIRA] (JBWS-3543) Relax SubjectCreatingPolicyInterceptor reaction to missing SecurityContext

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3543: ------------------------------------- Summary: Relax SubjectCreatingPolicyInterceptor reaction to missing SecurityContext Key: JBWS-3543 URL: https://issues.jboss.org/browse/JBWS-3543 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.1 Currently the org.jboss.wsf.stack.cxf.security.authentication.SubjectCreatingPolicyInterceptor throws exception if a SecurityContext is not available in the Message instance. It should however simply log the error and let the authentication fail later. The early throw of exception prevents WS-MEX from properly working for any endpoint this interceptor is attached to. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
1
0 / 0

[JBoss JIRA] (JBWS-3542) Allow WS-MetadataExchange in WS-Trust testcase

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3542: ------------------------------------- Summary: Allow WS-MetadataExchange in WS-Trust testcase Key: JBWS-3542 URL: https://issues.jboss.org/browse/JBWS-3542 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano 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 For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
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

11 years, 7 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 September 2012