Note

Access to this page requires authorization. You can try signing in or .

Access to this page requires authorization. You can try .

WS_SECURITY_HEADER_LAYOUT enumeration (webservices.h)

The layout rules applied to the elements of the WS-Security security header. This setting is relevant to message security bindings and mixed-mode security bindings.

Syntax

typedef enum {
 WS_SECURITY_HEADER_LAYOUT_STRICT = 1,
 WS_SECURITY_HEADER_LAYOUT_LAX = 2,
 WS_SECURITY_HEADER_LAYOUT_LAX_WITH_TIMESTAMP_FIRST = 3,
 WS_SECURITY_HEADER_LAYOUT_LAX_WITH_TIMESTAMP_LAST = 4
} WS_SECURITY_HEADER_LAYOUT;

Constants

 
WS_SECURITY_HEADER_LAYOUT_STRICT
Value: 1
The elements of the security header must follow a 'declare before use'
layout. All security tokens must appear before their usage.
WS_SECURITY_HEADER_LAYOUT_LAX
Value: 2
The elements of the security header can be in arbitrary order,
including security tokens appearing after usage.
WS_SECURITY_HEADER_LAYOUT_LAX_WITH_TIMESTAMP_FIRST
Value: 3
The elements of the security header can be in arbitrary order as in WS_SECURITY_HEADER_LAYOUT_LAX, but the timestamp element must
be the first element.
WS_SECURITY_HEADER_LAYOUT_LAX_WITH_TIMESTAMP_LAST
Value: 4
The elements of the security header can be in arbitrary order as in WS_SECURITY_HEADER_LAYOUT_LAX, but the timestamp element must
be the last element.

Requirements

Requirement Value
Minimum supported client Windows 7 [desktop apps only]
Minimum supported server Windows Server 2008 R2 [desktop apps only]
Header webservices.h

Feedback

Was this page helpful?

Additional resources

  • Last updated on