WAS v8.5 > Secure applications > Secure web services > Secure web services > Web Services Security concepts > Web Services Security concepts > What is new for securing web services

Web Services Security specification - a chronology

The development of the Web Services Security specification includes information on the Organization for the OASIS Web Services Security specification. The OASIS Web Services Security specification serves as a basis for securing web services in WebSphere Application Server.

Best practice: IBM WAS supports the JAX-WS programming model and JAX-RPC. JAX-WS is the next generation web services programming model extending the foundation provided by JAX-RPC. Using the strategic JAX-WS programming model, development of web services and clients is simplified through support of a standards-based annotations model. Although JAX-RPC and applications are still supported, take advantage of the easy-to-implement JAX-WS programming model to develop new web services applications and clients. best-practices

Advantages of using JAX-WS in WAS include:


Non-OASIS activities

Web services is gaining rapid acceptance as a viable technology for interoperability and integration. However, securing web services is one of the paramount quality of services that makes the adoption of web services a viable industry and commercial solution for businesses. IBM and Microsoft jointly published a security white paper on web services entitled Security in a Web Services World: A Proposed Architecture and Roadmap. The white paper discusses the following initial and subsequent specifications in the proposed Web Services Security roadmap:

Web service security

This specification defines how to attach a digital signature, use encryption, and use security tokens in SOAP messages.

WS-Policy

This specification defines the language used to describe security constraints and the policy of intermediaries or endpoints.

WS-Trust

This specification defines a framework for trust models to establish trust between web services.

WS-Privacy

This specification defines a model of how to express a privacy policy for a web service and a requester.

WS-SecureConversation

This specification defines how to exchange and establish a secured context, which derives session keys between web services.

WS-Authorization

This specification defines the authorization policy for a Web service. However, the WS-Authorization specification has not been published. The existing implementation of Web Services Security is based upon the Web Services for Java EE or Java Specification Requirements (JSR) 109 specification. The implementation of Web Services Security leverages the Java EE role-based authorization checks. For conceptual information, read about role-based authorization. If you develop a web service that requires method-level authorization checks, then use stateless session beans to implement the web service. For more information, read about securing enterprise bean applications.

If you develop a web service that is implemented as a servlet, we can use coarse-grained or URL-based authorization in the web container. However, in this situation, we cannot use the identity from Web Services Security for authorization checks. Instead, we can use the identity from the transport. If we use SOAP over HTTP, then the identity is in the HTTP transport.

This following figure shows the relationship between these specifications:

In April 2002, IBM, Microsoft, and VeriSign proposed the WS-Security specification on their websites as depicted by the green box in the previous figure. This specification included the basic ideas of a security token, XML digital signature, and XML encryption. The specification also defined the format for user name tokens and encoded binary security tokens. After some discussion and an interoperability test based on the specification, the following issues were noted:

In August 2002, IBM, Microsoft, and VeriSign published the Web Services Security Addendum, which attempted to address the previously listed issues. The following solutions were addressed in the addendum:

The specifications for the blue boxes in the previous figure have been proposed by various industry vendors and various interoperability events have been organized by the vendors to verify and refine the proposed specifications.


OASIS activities

In June 2002, OASIS received a proposed Web Services Security specification from IBM, Microsoft, and VeriSign. The Web Services Security Technical Committee (WSS TC) was organized at OASIS soon after the submission. The technical committee included many companies including IBM, Microsoft, VeriSign, Sun Microsystems, and BEA Systems.

In September 2002, WSS TC published its first specification, Web Services Security Core Specification, Working Draft 01. This specification included the contents of both the original Web Services Security specification and its addendum.

The coverage of the technical committee became larger as the discussion proceeded. Because the Web Services Security Core Specification allows arbitrary types of security tokens, proposals were published as profiles. The profiles described the method for embedding tokens, including SAML tokens and Kerberos tokens embedded into the Web Services Security messages. Subsequently, the definitions of the usage for user name tokens and X.509 binary security tokens, which were defined in the original Web Services Security Specification, were divided into the profiles.

WAS Versions 5.0.2, 5.1, and 5.1.1 support the following specifications:

In April 2004, the Web Service Security specification (officially called Web Services Security: SOAP Message Security v1.0) became the v1.0 OASIS standard. Also, the Username token and X.509 token profiles are v1.0 specifications. WAS 6 and later support the following Web Services Security specifications from OASIS:

In February 2006, the core Web Service Security specification was updated and became the v1.1 OASIS standard. Also, the Username token, X.509 token profile, and Kerberos token profile were updated to the v1.1 specifications. Portions of the following Web Services Security specifications from OASIS are supported in WAS, specifically signature confirmation, encrypted header, and thumbprint references:

The following specification describes the use of Kerberos tokens with respect to the Web Services Security message security specifications. The specification defines how to use a Kerberos token to support authentication and message protection: OASIS: Web Services Security Kerberos Token Profile 1.1 OASIS Standard Specification, 1 February 2006.

In 2007, the OASIS Web Services Secure Exchange Technical Committee (WS-SX) produced and approved the following specifications. Portions of these specifications are supported by WAS v7 and later.

The following figure shows the various Web Services Security-related specifications.

WAS also provides plug-in capability to enable security providers to extend the runtime capability and implement some of the higher level specifications in the Web Service Security stack. The plug-in points are exposed as Service Provider Programming Interfaces (SPI). For more information on these SPIs, see Default implementations of the Web Services Security service provider programming interfaces.


Web Services Security specification 1.0 development

The OASIS Web Services Security specification is based upon the following World Wide Web Consortium (W3C) specifications. Most of the W3C specifications are in the standard body recommended status.

These specifications are supported in WAS in the context of Web Services Security. For example, we can sign a SOAP message by specifying the integrity option in the deployment descriptors. There is a client side API that an application can use to enable Web Services Security for securing a SOAP message.

The OASIS Web Services Security v1.0 specification defines the enhancements used to provide message integrity and confidentiality. It also provides a general framework for associating the security tokens with a SOAP message. The specification is designed to be extensible to support multiple security token formats. The particular security token usage is addressed with the security token profile.


Specification and profile support in WAS

OASIS is working on various profiles. For more information, see Organization for the Advancement of Structured Information Standards Committees.

The following list includes of the published draft profiles and OASIS Web Services Security technical committee work in progress.

WAS does not support these profiles:

Support for Web Services Security draft 13 and Username token profile draft 2 is deprecated in WAS 5.0.2, 5.1.0 and 5.1.1. For migration information, see Migrating JAX-RPC Web Services Security applications to v8.5 applications.

The wire format of the SOAP message with Web Services Security in Web Services Security v1.0 has changed and is not compatible with previous drafts of the OASIS Web Services Security specification. Interoperability between OASIS Web Services Security v1.0 and previous Web Services Security drafts is not supported. However, it is possible to run an application based on Web Services Security draft 13 on WAS v6 and later. The application can interoperate with an application based on Web Services Security draft 13 on WAS v5.0.2, 5.1 or 5.1.1.

WAS supports both the OASIS Web Services Security draft 13 and the OASIS Web Services Security 1.0 specification. But in WAS v6 and later, the support of OASIS Web Services Security draft 13 is deprecated. However, applications that were developed using OASIS Web Services Security draft 13 on WAS 5.0.2, 5.1.0 and 5.1.1 can run on WAS v6 and later. OASIS Web Services Security v1.0 support is available only for Java EE v1.4 and later applications. The configuration format for the deployment descriptor and the binding is different from previous versions of WAS. You must migrate the existing applications to Java EE 1.4 and migrate the Web Services Security configuration to the WAS v6 format.


Other Web Services Security specifications development

The most recently updated versions of the following OASIS Web Services Security specifications are supported in WAS in the context of Web Services Security:


Web Services Interoperability Organization (WS-I) activities

Web Services Interoperability Organization (WS-I) is an open industry effort to promote web services interoperability across vendors, platforms, programming languages and applications. The organization is a consortium of companies across many industries including IBM, Microsoft, Oracle, Sun, Novell, VeriSign, and Daimler Chrysler. WS-I began working on the basic security profile (BSP) in the spring of 2003. BSP consists of a set of non-proprietary web services specifications that clarifies and amplifies those specifications to promote Web Services Security interoperability across different vendor implementations. As of June 2004, BSP is a public draft. For more information, see the Web Services Interoperability Organization web page.

Specifically, see Basic Security Profile v1.0 for details about the BSP. WAS supports compliance with the BSP draft, but Web Services Security does not support the BSP v1.1 draft. See Basic Security Profile compliance tips for the details to configure the application in compliance with the BSP draft.


Related concepts:

Default implementations of the Web Services Security service provider programming interfaces
Role-based authorization
Basic Security Profile compliance tips


Related


Migrating JAX-RPC Web Services Security applications to v8.5 applications
Implement web services applications with JAX-WS
Implement web services applications with JAX-RPC
Secure enterprise bean applications


+

Search Tips   |   Advanced Search