Username_Over_Transport
The Username_Over_Transport policy uses a Username token to provide client authentication with Transport binding and includes a Timestamp token to guard against replay attacks. The entire message is secured by the HTTPS transport protocol. This policy does not enforce signatures or encryption.
When the policy is attached to: | Message type | To enforce the policy, Integration Server... |
Consumer web service descriptor | outbound request | ![*](chapterTOC_bullet.png) Adds a Timestamp token to the security header. Integration Server determines the timestamp expiration date to specify using the WS Security Properties of the endpoint alias or by using watt.server.ws.security server configuration parameters. For more information, see webMethods Integration Server Administrator’s Guide. |
| inbound response | ![*](chapterTOC_bullet.png) Requires a signed Timestamp token, which Integration Server validates to ensure against replay attacks. |
Provider web service descriptor | inbound request | ![*](chapterTOC_bullet.png) Requires a Username token in the security header. Integration Server authenticates the sender of the inbound request messages using the user name supplied in Username token. ![*](chapterTOC_bullet.png) Requires a signed Timestamp token in the security header, which Integration Server validates to ensure against replay attacks. |
| outbound response | Adds a Timestamp token to the security header. Integration Server determines the timestamp expiration date to specify using the WS Security Properties of the endpoint alias or by using watt.server.ws.security server configuration parameters. For more information, see webMethods Integration Server Administrator’s Guide. |