Uploaded image for project: 'JBoss Web Services'
  1. JBoss Web Services
  2. JBWS-498

Vote for BasicSecurityProfile-1.0

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Done
    • Icon: Major Major
    • jbossws-voting
    • None
    • productization
    • None

      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.

              Unassigned Unassigned
              tdiesler@redhat.com Thomas Diesler
              Votes:
              9 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: