Web Services Security configuration considerations
To secure web services for WebSphere® Application Server, you must specify several different configurations. Although there is not a specific sequence in which you must specify these different configurations, some configurations reference other configurations.
最佳作法: IBM® WebSphere Application Server 支援 Java™ API for XML 型 Web 服務 (JAX-WS) 程式設計模型和 Java API for XML 型 RPC (JAX-RPC) 程式設計模型。JAX-WS 是延伸 JAX-RPC 程式設計模型所提供之基礎的下一代 Web 服務程式設計模型。
當使用策略性 JAX-WS 程式設計模型時,透過支援標準型註釋模型,簡化了 Web 服務和用戶端的開發工作。
雖然仍支援 JAX-RPC 程式設計模型和應用程式,但請利用易於實作的 JAX-WS 程式設計模型來開發新的 Web 服務應用程式和用戶端。best-practicesYou can configure Web Services Security on the application level and the server level. The following table shows an example of the relationships between each of the configurations that apply to just the application, to an entire server. However, the requirements for the bindings depend upon the deployment descriptor. Some binding information depends upon other information in the binding or server-level configuration. Within the table, the configurations in the Referenced configurations column are referenced by the configuration listed in the Configuration name column. For example, the token generator on the application-level for the request generator references the collection certificate store, the nonce, time stamp, and callback handler configurations.
| Configuration level | Configuration name | Referenced configurations |
|---|---|---|
| Application-level request generator | Token generator |
|
| Application-level request generator | Key information |
|
| Application-level request generator | Signing information |
|
| Application-level request generator | Encryption information |
|
| Application-level request consumer | Token consumer |
|
| Application-level request consumer | Key information |
|
| Application-level request consumer | Signing information |
|
| Application-level request consumer | Encryption information |
|
| Application-level response generator | Token generator |
|
| Application-level response generator | Key information |
|
| Application-level response generator | Signing information |
|
| Application-level response generator | Encryption information |
|
| Application-level response consumer | Token consumer |
|
| Application-level response consumer | Key information |
|
| Application-level response consumer | Signing information |
|
| Application-level response consumer | Encryption information |
|
| Server-level default generator bindings | Token generator |
|
| Server-level default generator bindings | Key information |
|
| Server-level default generator bindings | Signing information |
|
| Server-level default generator bindings | Encryption information |
|
| Server-level default consumer bindings | Token consumer |
|
| Server-level default consumer bindings | Key information |
|
| Server-level default consumer bindings | Signing information |
|
| Server-level default consumer bindings | Encryption information |
|
When multiple applications will use the same binding information, consider configuring the binding information on the server level. For example, you might have a global key locator configuration that is used by multiple applications. Configuration information for the application-level precedes similar configuration information on the server-level.
參照主題