January 2008 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Updated: (JBWS-1545) WS-Federation support

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1545?page=all ] Thomas Diesler updated JBWS-1545: --------------------------------- Fix Version/s: jbossws-3.x (was: jbossws-3.0.1) > WS-Federation support > --------------------- > > Key: JBWS-1545 > URL: http://jira.jboss.com/jira/browse/JBWS-1545 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: William DeCoste > Fix For: jbossws-3.x > > > Intuit request. Notes: > Support of single sign-on using Liberty, SAML and WS-Federation. > Support of SAML profile. -- 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] Updated: (JBWS-926) JBoss to JBoss binary optimiztion

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-926?page=all ] Thomas Diesler updated JBWS-926: -------------------------------- Fix Version/s: jbossws-3.x (was: jbossws-3.0.1) > JBoss to JBoss binary optimiztion > --------------------------------- > > Key: JBWS-926 > URL: http://jira.jboss.com/jira/browse/JBWS-926 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: Thomas Diesler > Fix For: jbossws-3.x > > > With WS the client and server are fundamentally disconnected and exchange XML documents that are valid in the context of the abstract contract defined in WSDL. Having said that, client/server implementations might not care about the abstract contract as long as there are no handlers involved that work on the SAAJ/DOM API. Currently all transport concerns are delegated to jboss-remoting. It would therefore be possible to implement a binary transfer of the SOAPMessage that is linked to a remoting protocol other than HTTP. -- 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] Updated: (JBWS-1550) biometric authentication support

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1550?page=all ] Thomas Diesler updated JBWS-1550: --------------------------------- Fix Version/s: jbossws-3.x (was: jbossws-3.0.1) > biometric authentication support > -------------------------------- > > Key: JBWS-1550 > URL: http://jira.jboss.com/jira/browse/JBWS-1550 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: William DeCoste > Fix For: jbossws-3.x > > > Intuit request. Notes: > Desktop client presents user credentials to the server to assure confidentiality of user identity. > The Desktop Client can be either a .NET client or a Java rich client. The Server is a business service running Java Web services using a Java EE Web / application server. > The user credentials can be username tokens (e.g. user id and password), certificate tokens (e.g. X.509v3 certificates), binary tokens (e.g. biometrics, fingerprint). Certificate tokens or binary tokens are often used multi-factor authentication to assure confidentiality and to meet compliance requirements. > ------------------------------------------------------------------------------------\ > Web browser presents user credentials to the server to assure confidentiality of user identity. > The Web browser can be Microsoft Internet Explorer, or Firefox Web browser. The Server is a business service running Java Web services using a Java EE Web / application server. > The user credentials can be username tokens (e.g. user id and password), digital certificates tokens (e.g. X.509v3 certificates), or binary tokens (e.g. biometrics, fingerprint). Certificate tokens or binary tokens are often used multi-factor authentication to assure confidentiality and to meet compliance requirements. > -------------------------------------------------------------------------------------- > Third party presents user credentials via Web service to the server to assure confidentiality. > Third party can be a remote trusted host (e.g. third party application), hosted application (e.g. in remote data center) or a trusted service provider that interact with Intuit Web services. > The Web service can be SOAP or REST Web service. The Server is a business service running Java Web services using a Java EE Web / application server. > The user credentials can be username tokens (e.g. user id and password), digital certificates tokens (e.g. X.509v3 certificates), binary tokens (e.g. biometrics, fingerprint) or a mixture of these tokens (as in multi-factor authentication). -- 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] Updated: (JBWS-461) WS-Transaction section in user guide backed up by sample code

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-461?page=all ] Thomas Diesler updated JBWS-461: -------------------------------- Fix Version/s: jbossws-3.x (was: jbossws-3.0.1) > WS-Transaction section in user guide backed up by sample code > ------------------------------------------------------------- > > Key: JBWS-461 > URL: http://jira.jboss.com/jira/browse/JBWS-461 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: ws-transaction > Reporter: Thomas Diesler > Fix For: jbossws-3.x > > > Integrate the Arjuna WS-Tx with JBossWS. > There should be a tests-transaction target in the jbossws testsuite. -- 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] Updated: (JBWS-1542) WS-Security Policy support

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1542?page=all ] Thomas Diesler updated JBWS-1542: --------------------------------- Fix Version/s: jbossws-3.x (was: jbossws-3.0.1) > WS-Security Policy support > -------------------------- > > Key: JBWS-1542 > URL: http://jira.jboss.com/jira/browse/JBWS-1542 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: William DeCoste > Fix For: jbossws-3.x > > > Intuit request. Notes: > If WSS 1.1 is used, use WS-policy and WS-security policy to allow interoperability. > WS-Policy is implemented in JBossWS 1.2; however, there is currently no way of using it. It is expected that WS-Policy support will be available in JBossWS 1.2.1 (See "JBWS-856" in JIRA). > WS-Security Policy is not implemented -- 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] Updated: (JBWS-1202) Allow HttpSession timeout to be set of EJB endpoints.

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1202?page=all ] Thomas Diesler updated JBWS-1202: --------------------------------- Fix Version/s: jbossws-3.x (was: jbossws-3.0.1) > Allow HttpSession timeout to be set of EJB endpoints. > ----------------------------------------------------- > > Key: JBWS-1202 > URL: http://jira.jboss.com/jira/browse/JBWS-1202 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-native > Affects Versions: jbossws-1.0.3 > Reporter: Darran Lofthouse > Fix For: jbossws-3.x > > > Allow HttpSession timeout to be set of EJB endpoints, currently this can only be set for POJO endpoints as they already have a war. -- 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] Updated: (JBWS-1216) 4.22 Use of the Catalog

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1216?page=all ] Thomas Diesler updated JBWS-1216: --------------------------------- Fix Version/s: jbossws-3.x (was: jbossws-3.0.1) > 4.22 Use of the Catalog > ----------------------- > > Key: JBWS-1216 > URL: http://jira.jboss.com/jira/browse/JBWS-1216 > Project: JBoss Web Services > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: Thomas Diesler > Fix For: jbossws-3.x > > -- 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] Updated: (JBWS-1030) Add propper MC dependencies for JMX services that are required.

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1030?page=all ] Thomas Diesler updated JBWS-1030: --------------------------------- Fix Version/s: jbossws-3.x (was: jbossws-3.0.1) > Add propper MC dependencies for JMX services that are required. > --------------------------------------------------------------- > > Key: JBWS-1030 > URL: http://jira.jboss.com/jira/browse/JBWS-1030 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: Jason T. Greene > Fix For: jbossws-3.x > > -- 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] Updated: (JBWS-515) Provide an initial implementation for WS-ReliableMessaging

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-515?page=all ] Thomas Diesler updated JBWS-515: -------------------------------- Fix Version/s: jbossws-native-2.0.4 (was: jbossws-3.0.1) > Provide an initial implementation for WS-ReliableMessaging > ---------------------------------------------------------- > > Key: JBWS-515 > URL: http://jira.jboss.com/jira/browse/JBWS-515 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: ws-reliable > Reporter: Thomas Diesler > Assigned To: Richard Opalka > Fix For: jbossws-native-2.0.4 > > > The relevant spec is > http://docs.oasis-open.org/ws-rx/wsrm/v1.1/wsrm.html > To complete this task we need > #1 An initial implementation of WS-RM Version 1.1 > #2 A comprehensive sample test case that shows the usage of WS-RM with JBossWS > #3 Documentation about WS-RM with JBossWS on the Wiki -- 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] Updated: (JBWS-1188) Relax requirement for wsu:id for UsernameToken

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1188?page=all ] Thomas Diesler updated JBWS-1188: --------------------------------- Fix Version/s: jbossws-native-2.0.4 (was: jbossws-3.0.1) > Relax requirement for wsu:id for UsernameToken > ---------------------------------------------- > > Key: JBWS-1188 > URL: http://jira.jboss.com/jira/browse/JBWS-1188 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ws-security > Affects Versions: jbossws-1.0.3 > Reporter: Darran Lofthouse > Assigned To: Darran Lofthouse > Fix For: jbossws-native-2.0.4 > > > The JBossWS UsernameToken implementation is mandating that the wsu:id attribute is present on incomming requests. > Some thirdparty web services stacks being used as clients to JBossWS do not send the ID so we are rejecting the request. Additionally we do not actually use the id anywhere anyway. > The requirement for the id should be relaxed. -- 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues January 2008