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

Vote for WS-Security

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Done
    • Icon: Major Major
    • jbossws-1.0RC2
    • None
    • jbossws-native
    • None

      Please vote for WS-Security if this is relevant to your enterprise web services

      http://www-128.ibm.com/developerworks/webservices/library/ws-secure/

      WS-Security describes enhancements to SOAP messaging to provide quality of protection through message integrity, message confidentiality, and single message authentication. These mechanisms can be used to accommodate a wide variety of security models and encryption technologies.

      WS-Security also provides a general-purpose mechanism for associating security tokens with messages. No specific type of security token is required by WS-Security. It is designed to be extensible (e.g. support multiple security token formats). For example, a client might provide proof of identity and proof that they have a particular business certification.

      Additionally, WS-Security describes how to encode binary security tokens. Specifically, the specification describes how to encode X.509 certificates and Kerberos tickets as well as how to include opaque encrypted keys. It also includes extensibility mechanisms that can be used to further describe the characteristics of the credentials that are included with a message.

      There are also other security specifications around, have a look at

      http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnglobspec/html/wssecurspecindex.asp

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

                Created:
                Updated:
                Resolved: