January 2008 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-1874) Allow configuration of secret key wrap algorithm

by Alessio Soldano (JIRA)

Allow configuration of secret key wrap algorithm ------------------------------------------------ Key: JBWS-1874 URL: http://jira.jboss.com/jira/browse/JBWS-1874 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ws-security Affects Versions: jbossws-2.0.1 Reporter: Alessio Soldano Assigned To: Alessio Soldano WCF wsse interoperability test 3.3 (November 2007) requires the mutual secret key to be wrapped with the RSA-OAEP algorithm. The current implementation always wraps the key with the RSA v1.5 algorithm (despite being able to unwrap using any algorithm). It should be possible to specify the key wrap algorithm in the wsse configuration files. -- 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

16 years, 10 months

1
4
0 / 0

[JBoss JIRA] Commented: (JBWS-1257) Add configuration for token references

by Alessio Soldano (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1257?page=comments#action_12396209 ] Alessio Soldano commented on JBWS-1257: --------------------------------------- http://jbws.dyndns.org/mediawiki/index.php?title=WS-Security_options#Toke... > Add configuration for token references > -------------------------------------- > > Key: JBWS-1257 > URL: http://jira.jboss.com/jira/browse/JBWS-1257 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: ws-security > Reporter: Jason T. Greene > Assigned To: Alessio Soldano > Fix For: jbossws-native-2.0.3 > > > Indigo does not support local BSTs for encryption, add support for specifiying the type of reference (issuerserial, identifier, etc). -- 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1960) Patch wiki2xml image link support

by Alessio Soldano (JIRA)

Patch wiki2xml image link support --------------------------------- Key: JBWS-1960 URL: http://jira.jboss.com/jira/browse/JBWS-1960 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: productization Reporter: Alessio Soldano Assigned To: Alessio Soldano Currently installed version of wiki2xml plug-in supports images links however wrong url are produced in docbook xml output. Example: [[Image:Deployment.jpg|left|border|700px|Ordered execution of deployment aspects]] is converted to <mediaobject> <imageobject> <imagedata fileref="http:///images/5/5d/Deployment.jpg"/> </imageobject> <textobject> <phrase>Ordered execution of deployment aspects</phrase> </textobject> </mediaobject> Of course this causes the resulting documentation to have broken image links. Ideally the plug-in should be able to produce absolute url with the current installation path; otherwise we might have a custom parameter in the launch form the user might use to set the prefix for url generation. -- 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBWS-1136) Allow username to be specified in the requires list

by Alessio Soldano (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1136?page=comments#action_12395725 ] Alessio Soldano commented on JBWS-1136: --------------------------------------- Given I agree with you about what you say on POJO endpoints, we could nevertheless do what the issue title says i.e. allowing a username element in the require list of the wsse configuration the same way we have for the timestamp, for example. This way we could reject requests that do not have a Username Token. What do you think about? > Allow username to be specified in the requires list > --------------------------------------------------- > > Key: JBWS-1136 > URL: http://jira.jboss.com/jira/browse/JBWS-1136 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: ws-security > Affects Versions: jbossws-1.0.1 > Reporter: Darran Lofthouse > Fix For: community contributions > > > Allow username to be specified in the requires list for endpoints so that messages without the username can be rejected. > At the moment for EJB endpoints they can be configured using standard J2EE security so if there is no authenticated user the request is rejected, however this can't be done for the POJO endpoints. -- 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBWS-1124) Scoped class loading domains for WS endpoints

by Heiko Braun (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1124?page=all ] Heiko Braun reopened JBWS-1124: ------------------------------- Assignee: Heiko Braun (was: Thomas Diesler) > Scoped class loading domains for WS endpoints > --------------------------------------------- > > Key: JBWS-1124 > URL: http://jira.jboss.com/jira/browse/JBWS-1124 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: Thomas Diesler > Assigned To: Heiko Braun > Fix For: jbossws-1.0.3 > > > Investigate scoped classloading domains -- 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1957) WS-Eventing extension sends incorrect HTTP content-type

by Heiko Braun (JIRA)

WS-Eventing extension sends incorrect HTTP content-type ------------------------------------------------------- Key: JBWS-1957 URL: http://jira.jboss.com/jira/browse/JBWS-1957 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: ws-eventing Affects Versions: jbossws-2.0.2 Reporter: Heiko Braun Assigned To: Heiko Braun Fix For: jbossws-native-2.0.4 Dan Retzlaff wrote: The Subscription class in org.jboss.ws.extensions.eventing.mgmt contains hard-coded SOAP 1.2 envelopes for event notification and SubscriptionEnd messages. However, SOAPConnectionImpl::callOneWay() sets the HTTP content-type to "text/xml". (More specifically, SOAPMessageImpl::saveChanges() does.) The SOAP 1.2 specification (7.1.4) and RFC 3902 require that SOAP HTTP bindings use a content-type of "application/soap+xml". This appears to be a bug. In my case, it manifests itself by when Axis2 throws a SOAPProcessingException complaining that incoming transport level information do not match the SOAP namespace. I would suggest that Subscription provide the correct content-type in a MimeHeaders object to its MessageFactory::createMessage() call, but SOAPMessageImpl::saveChanges() overwrites the value indiscriminately. Is changing those hard-coded envelopes to SOAP 1.1 the best solution here? It seems like we should be able to make SOAP 1.2 work... -- 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1956) Parametrize Records Management

by Thomas Diesler (JIRA)

Parametrize Records Management ------------------------------ Key: JBWS-1956 URL: http://jira.jboss.com/jira/browse/JBWS-1956 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: productivity Reporter: Thomas Diesler Assigned To: Thomas Diesler Fix For: jbossws-3.0.0 Currently the recorders are hard coded in the frameworks deployment aspect public void create(Deployment dep) { for (Endpoint ep : dep.getService().getEndpoints()) { /** Memory buffer recorder **/ MemoryBufferRecorder memoryRecorder = new MemoryBufferRecorder(); memoryRecorder.setName("MemoryBufferRecorder"); this.registerRecordProcessor(memoryRecorder, ep); /** Log recorder **/ LogRecorder logRecorder = new LogRecorder(); logRecorder.setName("LogRecorder"); this.registerRecordProcessor(logRecorder, ep); List<RecordProcessor> recordProcessorList = new LinkedList<RecordProcessor>(); recordProcessorList.add(memoryRecorder); recordProcessorList.add(logRecorder); ep.setRecordProcessors(recordProcessorList); } } This should be paramertized here <bean name="WSNativeEndpointRecordProcessorDeploymentAspect" class="org.jboss.wsf.framework.deployment.EndpointRecordProcessorDeploymentAspect"> <property name="mbeanServer"><inject bean="WSMBeanServerLocator" property="mbeanServer"/></property> <property name="requires">RegisteredEndpoint</property> <property name="provides">EndpointRecordProcessors</property> </bean> and documented accordingly. Reading the documentation it was not clear to me how I would enable this feature. Then I figured that I need to go to a deployed endpoint and manually enable recording for a specific endpoint. -- 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

16 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-1954) Include Metro specific tests in hudson QA

by Thomas Diesler (JIRA)

Include Metro specific tests in hudson QA ----------------------------------------- Key: JBWS-1954 URL: http://jira.jboss.com/jira/browse/JBWS-1954 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-metro Reporter: Thomas Diesler Fix For: jbossws-metro-1.0.0 -- 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1381) Disable HTTP chunking for J2ME client s

by Thomas Diesler (JIRA)

Disable HTTP chunking for J2ME client s --------------------------------------- Key: JBWS-1381 URL: http://jira.jboss.com/jira/browse/JBWS-1381 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jaxrpc Reporter: Thomas Diesler Assigned To: Thomas Diesler Fix For: jbossws-1.0.5 How do I disable HTTP chunking for my EJB3 webservices? I am using @WebMethod etc. I need to disable HTTP chunking because my J2ME client (the wireless toolkit) can't handle chunking yet. -- 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

16 years, 10 months

4
8
0 / 0

[JBoss JIRA] Created: (JBWS-1953) Release spi, common and framework

by Thomas Diesler (JIRA)

Release spi, common and framework --------------------------------- Key: JBWS-1953 URL: http://jira.jboss.com/jira/browse/JBWS-1953 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assigned To: Heiko Braun Fix For: jbossws-3.0.0 -- 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

16 years, 10 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 January 2008