3.1.4.1.23 Metadata and Discovery

The WS-Management specification defines a mechanism to determine the existence of a WS-Management service on a server. More information is specified in [DMTF-DSP0226] section 11.

The Web Services Management Protocol Extensions for Windows Vista service MUST <71>support the WS-Management discovery mechanism as specified in [DMTF-DSP0226] section 11, when the request is authenticated.

The Web Services Management Protocol Extensions for Windows Vista service MUST <72>support the WS-Management discovery mechanism as specified in [DMTF-DSP0226] section 11, when the request is unauthenticated and the following HTTP header is present.

     WSMANIDENTIFY: unauthenticated

The Web Services Management Protocol Extensions for Windows Vista service SHOULD<73> return the enabled authentication mechanisms as a part of the Identify response using the wsmid:SecurityProfiles element as specified in [DMTF-DSP0226] section 11. The wsmid:SecurityProfiles element MUST NOT be returned when the request is unauthenticated.

If the wsmid:SecurityProfiles element is present, the following MUST be included as child elements of the wsmid:SecurityProfiles element, if Basic authentication is enabled as specified in section 3.1.4.1.29.2. The following MUST NOT be included if Basic authentication is disabled.

 <wsmid:SecurityProfileName>
   http://schemas.dmtf.org/wbem/wsman/1/wsman/secprofile/http/basic
 </wsmid:SecurityProfileName>
 <wsmid:SecurityProfileName>
   http://schemas.dmtf.org/wbem/wsman/1/wsman/secprofile/https/basic
 </wsmid:SecurityProfileName>

If the wsmid:SecurityProfiles element is present, the following MUST be included as child elements of the wsmid:SecurityProfiles element, if either Negotiate or Kerberos authentication is enabled as specified in section 3.1.4.1.29.2. The following MUST NOT be included if both Negotiate and Kerberos authentication are disabled.

 <wsmid:SecurityProfileName>
   http://schemas.dmtf.org/wbem/wsman/1/wsman/secprofile/http/spnego-kerberos
 </wsmid:SecurityProfileName>
 <wsmid:SecurityProfileName>
   http://schemas.dmtf.org/wbem/wsman/1/wsman/secprofile/https/spnego-kerberos
 </wsmid:SecurityProfileName>

If the wsmid:SecurityProfiles element is present, the following MUST be included as a child element of the wsmid:SecurityProfiles element, if Certificate authentication is enabled as specified in section 3.1.4.1.29.2. It MUST NOT be included if Certificate authentication is disabled.

 <wsmid:SecurityProfileName>
   http://schemas.dmtf.org/wbem/wsman/1/wsman/secprofile/https/mutual
 </wsmid:SecurityProfileName>

If the Web Services Management Protocol Extensions for Windows Vista service is compliant with the DASH Implementation Requirements version 1, it SHOULD include the dash:DASHVersion element in the IdentifyResponse message as specified in [DMTF-DSP0232-1.0.0] section 9.2.2, [DMTF-DSP0232-1.0.1] and [DMTF-DSP0232-1.1.0]. This compliance is detected in an implementation-specific way.<74>

If the Web Services Management Protocol Extensions for Windows Vista service is compliant with the SMASH Implementation Requirements version 1, it SHOULD include the following XML element as a child of the wsmid:IdentifyResponse element in the IdentifyResponse message.

 <SMASH:SMASHVersion>1.x.x</SMASH:SMASHVersion>

If this element is present, the value MUST be of the form "1.x.x" where "x.x" represents the highest version of the SMASH Implementation Requirements version 1 specification with which the service is compliant. This compliance is detected in an implementation-specific way. <75> The SMASH Implementation Requirements version 1 are as specified in [DMTF-DSP0217-1.0.0].

If the Web Services Management Protocol Extensions for Windows Vista service is compliant with the SMASH Implementation Requirements version 2, it SHOULD include the SMASH:SMASHVersion element in the IdentifyResponse message as specified in [DMTF-DSP0217-2.0.0] section 8.2.1. This compliance is detected in an implementation-specific way. <76>