June 2007 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Updated: (JBWS-498) Vote for BasicSecurityProfile-1.0

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-498?page=all ] Thomas Diesler updated JBWS-498: -------------------------------- Component/s: productization (was: ws-security) (was: jbossws-jaxws) > Vote for BasicSecurityProfile-1.0 > --------------------------------- > > Key: JBWS-498 > URL: http://jira.jboss.com/jira/browse/JBWS-498 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: productization > Reporter: Thomas Diesler > Fix For: jbossws-voting > > > Please vote for BasicSecurityProfile-1.0 if this is relevant to your enterprise web services > http://www.ws-i.org/Profiles/BasicSecurityProfile-1.0.html > Defines the WS-I Basic Security Profile 1.0 (hereafter, "Profile"), consisting of a set of non-proprietary Web services specifications, along with clarifications to and amplifications of those specifications which promote interoperability. > Section 1 introduces the Profile, and relates the philosophy that it takes with regard to interoperability. > Section 2, "Scope of the Profile," delimits the areas where the Profile improves interoperability. > Section 3, "Profile Conformance," explains what it means to be conformant to the Profile. > Each subsequent section addresses a component of the Profile, and consists of two parts; an overview detailing the component specifications and their extensibility points, followed by subsections that address individual parts of the component specifications. Note that there is no relationship between the section numbers in this document and those in the referenced specifications. > In order to secure a communication between two parties, the two parties must exchange security credentials (either directly or indirectly). However, each party needs to determine if they can "trust" the asserted credentials of the other party. This specification defines extensions to WS-Security for issuing and exchanging security tokens and ways to establish and access the presence of trust relationships. Using these extensions, applications can engage in secure communication designed to work with the general Web Services framework, including WSDL service descriptions, UDDI businessServices and bindingTemplates, and SOAP messages. -- 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-326) Vote for WS-Notification

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-326?page=all ] Thomas Diesler updated JBWS-326: -------------------------------- Component/s: productization (was: jbossws-jaxws) > Vote for WS-Notification > ------------------------ > > Key: JBWS-326 > URL: http://jira.jboss.com/jira/browse/JBWS-326 > Project: JBoss Web Services > Issue Type: Feature Request > Components: productization > Reporter: Thomas Diesler > Fix For: jbossws-voting > > > Please vote for WS-Notification if this is relevant to your enterprise web services > http://www-128.ibm.com/developerworks/library/specification/ws-notification > The Event-driven, or Notification-based, interaction pattern is a commonly used pattern for inter-object communications. Examples exist in many domains, for example in publish/subscribe systems provided by Message Oriented Middleware vendors, or in system and device management domains. This notification pattern is increasingly being used in a Web services context. > WS-Notification is a family of related white papers and specifications that define a standard Web services approach to notification using a topic-based publish/subscribe pattern. It includes: > * Standard message exchanges to be implemented by service providers that wish to participate in Notifications > * Standard message exchanges for a notification broker service provider > * Operational requirements expected of service providers and requestors that participate in notifications > * An XML model that describes topics. -- 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-503) Vote for WS-SecurityPolicy

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-503?page=all ] Thomas Diesler updated JBWS-503: -------------------------------- Component/s: productization (was: jbossws-jaxws) > Vote for WS-SecurityPolicy > -------------------------- > > Key: JBWS-503 > URL: http://jira.jboss.com/jira/browse/JBWS-503 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: productization > Reporter: Thomas Diesler > Fix For: jbossws-voting > > > Please vote for WS-SecurityPolicy if this is relevant to your enterprise web services > http://www-128.ibm.com/developerworks/library/specification/ws-secpol/ > The recently updated Web Services Security Policy Language (WS-SecurityPolicy) specification defines a set of security policy assertions which apply to Web Services Security: SOAP Message Security, WS-Trust, and WS-SecureConversation. This document takes the approach of defining a base set of assertions that describe how messages are to be secured. Flexibility with respect to token types, cryptographic algorithms, and mechanisms used, including using transport-level security, is part of the design and allows for evolution over time. The intent is to provide enough information for compatibility and interoperability to be determined by Web services participants, along with all information necessary to actually enable a participant to engage in a secure exchange of messages. -- 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-502) Vote for WS-PolicyAttachment

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-502?page=all ] Thomas Diesler updated JBWS-502: -------------------------------- Component/s: productization (was: jbossws-jaxws) > Vote for WS-PolicyAttachment > ---------------------------- > > Key: JBWS-502 > URL: http://jira.jboss.com/jira/browse/JBWS-502 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: productization > Reporter: Thomas Diesler > Fix For: jbossws-voting > > > Please vote for WS-PolicyAttachment if this is relevant to your enterprise web services > http://www-128.ibm.com/developerworks/library/specification/ws-polatt/ > WS-Policy provides a general purpose model and syntax to describe and communicate the policies of a Web service. > The Web Services Policy Framework (WS-Policy) specification defines an abstract model and an XML-based expression grammar for policies. This specification, Web Services Policy Attachment (WS-PolicyAttachment), defines two general-purpose mechanisms for associating such policies with the subjects to which they apply. This specification also defines how these general-purpose mechanisms can be used to associate WS-Policy with WSDL and UDDI descriptions. -- 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-491) Vote for SAMLTokenProfile-1.0

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-491?page=all ] Thomas Diesler updated JBWS-491: -------------------------------- Component/s: productization (was: jbossws-jaxws) (was: ws-security) > Vote for SAMLTokenProfile-1.0 > ----------------------------- > > Key: JBWS-491 > URL: http://jira.jboss.com/jira/browse/JBWS-491 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: productization > Reporter: Anil Saldhana > Fix For: jbossws-voting > > > There is a SAML Token Profile 1.0 defined by the WS-I organization. > http://www.ws-i.org/Profiles/SAMLTokenProfile-1.0.html > This references a SAML Token Profile from the WS-Security family at: > http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.0.pdf > This specification defines SAML 1.1 assertion tokens to be used in ws-security messages. > Please vote on this issue. -- 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-506) Vote for WS-Discovery

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-506?page=all ] Thomas Diesler updated JBWS-506: -------------------------------- Component/s: productization (was: jbossws-jaxws) > Vote for WS-Discovery > --------------------- > > Key: JBWS-506 > URL: http://jira.jboss.com/jira/browse/JBWS-506 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: productization > Reporter: Thomas Diesler > Fix For: jbossws-voting > > > Please vote for WS-Discovery if this is relevant to your enterprise web services > http://msdn.microsoft.com/library/en-us/dnglobspec/html/WS-Discovery.pdf > This specification defines a multicast discovery protocol to locate services. By default, probes are sent to a multicast group, and target services that match return a response directly to the requester. To scale to a large number of endpoints, the protocol defines the multicast suppression behavior if a discovery proxy is available on the network. To minimize the need for polling, target services that wish to be discovered send an announcement when they join and leave the network. -- 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-877) Vote for WS-SecureExchange

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-877?page=all ] Thomas Diesler updated JBWS-877: -------------------------------- Component/s: productization (was: jbossws-jaxws) (was: ws-security) > Vote for WS-SecureExchange > -------------------------- > > Key: JBWS-877 > URL: http://jira.jboss.com/jira/browse/JBWS-877 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: productization > Reporter: Heiko Braun > Fix For: jbossws-voting > > > Please vote for WS-SecureExchange if this is relevant to your enterprise web services > http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ws-sx > The purpose of the OASIS WS-SX TC is to define extensions to OASIS Web Services Security to enable trusted SOAP message exchanges involving multiple message exchanges and to define security policies that govern the formats and tokens of such messages. This work will be carried out through continued refinement of the Web Services SecureConversation, SecurityPolicy and Trust specifications submitted to the TC as referenced in this charter. -- 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-505) Vote for WS-Enumeration

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-505?page=all ] Thomas Diesler updated JBWS-505: -------------------------------- Component/s: productization (was: jbossws-jaxws) > Vote for WS-Enumeration > ----------------------- > > Key: JBWS-505 > URL: http://jira.jboss.com/jira/browse/JBWS-505 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: productization > Reporter: Thomas Diesler > Fix For: jbossws-voting > > > Please vote for WS-Enumeration if this is relevant to your enterprise web services > http://msdn.microsoft.com/library/en-us/dnglobspec/html/ws-enumeration.pdf > This specification describes a general SOAP-based protocol for enumerating a sequence of XML elements that is suitable for traversing logs, message queues, or other linear information models. -- 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-499) Vote for WS-Coordination

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-499?page=all ] Thomas Diesler updated JBWS-499: -------------------------------- Component/s: productization (was: jbossws-jaxws) > Vote for WS-Coordination > ------------------------ > > Key: JBWS-499 > URL: http://jira.jboss.com/jira/browse/JBWS-499 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: productization > Reporter: Thomas Diesler > Fix For: jbossws-voting > > > Please vote for WS-Coordination if this is relevant to your enterprise web services > http://www-128.ibm.com/developerworks/library/specification/ws-tx/ > This specification describes an extensible framework for providing protocols that coordinate the actions of distributed applications. Such coordination protocols are used to support a number of applications, including those that need to reach consistent agreement on the outcome of distributed activities. > The framework defined in this specification enables an application service to create a context needed to propagate an activity to other services and to register for coordination protocols. The framework enables existing transaction processing, workflow, and other systems for coordination to hide their proprietary protocols and to operate in a heterogeneous environment. > Additionally this specification describes a definition of the structure of context and the requirements for propagating context between cooperating services. -- 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-76) Vote for WS-Reliable Messaging

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-76?page=all ] Thomas Diesler updated JBWS-76: ------------------------------- Component/s: productization (was: jbossws-jaxws) > Vote for WS-Reliable Messaging > ------------------------------ > > Key: JBWS-76 > URL: http://jira.jboss.com/jira/browse/JBWS-76 > Project: JBoss Web Services > Issue Type: Feature Request > Components: productization > Reporter: Thomas Diesler > Fix For: jbossws-voting > > > Please vote for WS-ReliableMessaging if this is relevant to your enterprise web services > http://www-106.ibm.com/developerworks/library/ws-rm/ > This specification (WS-ReliableMessaging) describes a protocol that allows messages to be delivered reliably between distributed applications in the presence of software component, system, or network failures. The updates are based upon the suggestions collected from the WS-ReliableMessaging Feedback Workshop held in July 2003 and the Interoperability Workshop help in October 2003. The protocol is described in this specification in an independent manner allowing it to be implemented using different network transport technologies. To support interoperable Web services, a SOAP binding is defined within this specification. > The protocol defined in this specification depends upon other Web services specifications for the identification of service endpoint addresses and policies. How these are identified and retrieved are detailed within those specifications and are out of scope for this document. -- 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 June 2007