ࡱ > # U bjbjnn aa D T T T Ԗ X 4 T : 2 @ r r r . 9 9 9 9 9 9 9 $ = [@ * 9 9 r r H : r r 9 9 $ r L۫ . ` ~9 : 0 : @ @ $ $ @ $ 9 9 : @ B ֔ : [MS-OXWSPED]: Password Expiration Date Web Service Protocol
Intellectual Property Rights Notice for Open Specifications Documentation
Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages, standards as well as overviews of the interaction among each of these technologies.
Copyrights. This documentation is covered by Microsoft copyrights. Regardless of any other terms that are contained in the terms of use for the Microsoft website that hosts this documentation, you may make copies of it in order to develop implementations of the technologies described in the Open Specifications and may distribute portions of it in your implementations using these technologies or your documentation as necessary to properly document the implementation. You may also distribute in your implementation, with or without modification, any schema, IDLs, or code samples that are included in the documentation. This permission also applies to any documents that are referenced in the Open Specifications.
No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
Patents. Microsoft has patents that may cover your implementations of the technologies described in the Open Specifications. Neither this notice nor Microsoft's delivery of the documentation grants any licenses under those or any other Microsoft patents. However, a given Open Specification may be covered by Microsoft HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=214445" Open Specification Promise or the HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=214448" Community Promise. If you would prefer a written license, or if the technologies described in the Open Specifications are not covered by the Open Specifications Promise or Community Promise, as applicable, patent licenses are available by contacting HYPERLINK "mailto:iplg@microsoft.com" iplg@microsoft.com.
Trademarks. The names of companies and products contained in this documentation may be covered by trademarks or similar intellectual property rights. This notice does not grant any licenses under those rights. For a list of Microsoft trademarks, visit HYPERLINK "http://www.microsoft.com/trademarks" www.microsoft.com/trademarks.
Fictitious Names. The example companies, organizations, products, domain names, email addresses, logos, people, places, and events depicted in this documentation are fictitious. No association with any real company, organization, product, domain name, email address, logo, person, place, or event is intended or should be inferred.
Reservation of Rights. All other rights are reserved, and this notice does not grant any rights other than specifically described above, whether by implication, estoppel, or otherwise.
Tools. The Open Specifications do not require the use of Microsoft programming tools or programming environments in order for you to develop an implementation. If you have access to Microsoft programming tools and environments you are free to take advantage of them. Certain Open Specifications are intended for use in conjunction with publicly available standard specifications and network programming art, and assumes that the reader either is familiar with the aforementioned material or has immediate access to it.
Revision Summary
DateRevision HistoryRevision ClassComments10/07/20111.0NewReleased new document.01/20/20122.0MajorSignificantly changed the technical content.04/27/20122.0No changeNo changes to the meaning, language, or formatting of the technical content.07/16/20122.0No changeNo changes to the meaning, language, or formatting of the technical content.10/08/20122.1MinorClarified the meaning of the technical content.02/11/20132.1No changeNo changes to the meaning, language, or formatting of the technical content.07/26/20132.1No changeNo changes to the meaning, language, or formatting of the technical content.11/18/20132.1No changeNo changes to the meaning, language, or formatting of the technical content.02/10/20142.1No changeNo changes to the meaning, language, or formatting of the technical content.04/30/20143.0MajorSignificantly changed the technical content.07/31/20143.0No changeNo changes to the meaning, language, or formatting of the technical content.10/30/20143.1MinorClarified the meaning of the technical content.
Table of Contents
TOC \f \h \t "DSTOC1-1,1,DSTOC1-2,2,DSTOC1-3,3,DSTOC1-4,4,DSTOC1-5,5,DSTOC1-6,6,DSTOC1-7,7,DSTOC1-8,8,DSTOC1-9,9,DSTOC2-2,2,DSTOC2-3,3,DSTOC2-4,4,DSTOC2-5,5,DSTOC2-6,6,DSTOC2-7,7,DSTOC2-8,8,DSTOC2-9,9,DSTOC3-3,3,DSTOC3-4,4,DSTOC3-5,5,DSTOC3-6,6,DSTOC3-7,7,DST HYPERLINK \l "_Toc401432157" 1 Introduction PAGEREF _Toc401432157 \h 5
HYPERLINK \l "_Toc401432158" 1.1 Glossary PAGEREF _Toc401432158 \h 5
HYPERLINK \l "_Toc401432159" 1.2 References PAGEREF _Toc401432159 \h 5
HYPERLINK \l "_Toc401432160" 1.2.1 Normative References PAGEREF _Toc401432160 \h 5
HYPERLINK \l "_Toc401432161" 1.2.2 Informative References PAGEREF _Toc401432161 \h 6
HYPERLINK \l "_Toc401432162" 1.3 Overview PAGEREF _Toc401432162 \h 6
HYPERLINK \l "_Toc401432163" 1.4 Relationship to Other Protocols PAGEREF _Toc401432163 \h 6
HYPERLINK \l "_Toc401432164" 1.5 Prerequisites/Preconditions PAGEREF _Toc401432164 \h 7
HYPERLINK \l "_Toc401432165" 1.6 Applicability Statement PAGEREF _Toc401432165 \h 7
HYPERLINK \l "_Toc401432166" 1.7 Versioning and Capability Negotiation PAGEREF _Toc401432166 \h 7
HYPERLINK \l "_Toc401432167" 1.8 Vendor-Extensible Fields PAGEREF _Toc401432167 \h 8
HYPERLINK \l "_Toc401432168" 1.9 Standards Assignments PAGEREF _Toc401432168 \h 8
HYPERLINK \l "_Toc401432169" 2 Messages PAGEREF _Toc401432169 \h 9
HYPERLINK \l "_Toc401432170" 2.1 Transport PAGEREF _Toc401432170 \h 9
HYPERLINK \l "_Toc401432171" 2.2 Common Message Syntax PAGEREF _Toc401432171 \h 9
HYPERLINK \l "_Toc401432172" 2.2.1 Namespaces PAGEREF _Toc401432172 \h 9
HYPERLINK \l "_Toc401432173" 2.2.2 Messages PAGEREF _Toc401432173 \h 9
HYPERLINK \l "_Toc401432174" 2.2.3 Elements PAGEREF _Toc401432174 \h 9
HYPERLINK \l "_Toc401432175" 2.2.4 Complex Types PAGEREF _Toc401432175 \h 10
HYPERLINK \l "_Toc401432176" 2.2.5 Simple Types PAGEREF _Toc401432176 \h 10
HYPERLINK \l "_Toc401432177" 2.2.6 Attributes PAGEREF _Toc401432177 \h 10
HYPERLINK \l "_Toc401432178" 2.2.7 Groups PAGEREF _Toc401432178 \h 10
HYPERLINK \l "_Toc401432179" 2.2.8 Attribute Groups PAGEREF _Toc401432179 \h 10
HYPERLINK \l "_Toc401432180" 3 Protocol Details PAGEREF _Toc401432180 \h 11
HYPERLINK \l "_Toc401432181" 3.1 ExchangeServerPortType Server Details PAGEREF _Toc401432181 \h 11
HYPERLINK \l "_Toc401432182" 3.1.1 Abstract Data Model PAGEREF _Toc401432182 \h 11
HYPERLINK \l "_Toc401432183" 3.1.2 Timers PAGEREF _Toc401432183 \h 11
HYPERLINK \l "_Toc401432184" 3.1.3 Initialization PAGEREF _Toc401432184 \h 11
HYPERLINK \l "_Toc401432185" 3.1.4 Message Processing Events and Sequencing Rules PAGEREF _Toc401432185 \h 11
HYPERLINK \l "_Toc401432186" 3.1.4.1 GetPasswordExpirationDate Operation PAGEREF _Toc401432186 \h 11
HYPERLINK \l "_Toc401432187" 3.1.4.1.1 Messages PAGEREF _Toc401432187 \h 12
HYPERLINK \l "_Toc401432188" 3.1.4.1.1.1 GetPasswordExpirationDateSoapIn Message PAGEREF _Toc401432188 \h 12
HYPERLINK \l "_Toc401432189" 3.1.4.1.1.2 GetPasswordExpirationDateSoapOut Message PAGEREF _Toc401432189 \h 13
HYPERLINK \l "_Toc401432190" 3.1.4.1.2 Elements PAGEREF _Toc401432190 \h 13
HYPERLINK \l "_Toc401432191" 3.1.4.1.2.1 m:GetPasswordExpirationDate Element PAGEREF _Toc401432191 \h 14
HYPERLINK \l "_Toc401432192" 3.1.4.1.2.2 m:GetPasswordExpirationDateResponse Element PAGEREF _Toc401432192 \h 14
HYPERLINK \l "_Toc401432193" 3.1.4.1.3 Complex Types PAGEREF _Toc401432193 \h 14
HYPERLINK \l "_Toc401432194" 3.1.4.1.3.1 m:GetPasswordExpirationDateType Complex Type PAGEREF _Toc401432194 \h 14
HYPERLINK \l "_Toc401432195" 3.1.4.1.3.2 m:GetPasswordExpirationDateResponseMessageType PAGEREF _Toc401432195 \h 15
HYPERLINK \l "_Toc401432196" 3.1.4.1.4 Simple Types PAGEREF _Toc401432196 \h 15
HYPERLINK \l "_Toc401432197" 3.1.4.1.5 Attributes PAGEREF _Toc401432197 \h 15
HYPERLINK \l "_Toc401432198" 3.1.4.1.6 Groups PAGEREF _Toc401432198 \h 15
HYPERLINK \l "_Toc401432199" 3.1.4.1.7 Attribute Groups PAGEREF _Toc401432199 \h 15
HYPERLINK \l "_Toc401432200" 3.1.5 Timer Events PAGEREF _Toc401432200 \h 16
HYPERLINK \l "_Toc401432201" 3.1.6 Other Local Events PAGEREF _Toc401432201 \h 16
HYPERLINK \l "_Toc401432202" 4 Protocol Examples PAGEREF _Toc401432202 \h 17
HYPERLINK \l "_Toc401432203" 4.1 GetPasswordExpirationDate Request PAGEREF _Toc401432203 \h 17
HYPERLINK \l "_Toc401432204" 5 Security PAGEREF _Toc401432204 \h 18
HYPERLINK \l "_Toc401432205" 5.1 Security Considerations for Implementers PAGEREF _Toc401432205 \h 18
HYPERLINK \l "_Toc401432206" 5.2 Index of Security Parameters PAGEREF _Toc401432206 \h 18
HYPERLINK \l "_Toc401432207" 6 Appendix A: Full WSDL PAGEREF _Toc401432207 \h 19
HYPERLINK \l "_Toc401432208" 7 Appendix B: Full XML Schema PAGEREF _Toc401432208 \h 21
HYPERLINK \l "_Toc401432209" 8 Appendix C: Product Behavior PAGEREF _Toc401432209 \h 22
HYPERLINK \l "_Toc401432210" 9 Change Tracking PAGEREF _Toc401432210 \h 23
HYPERLINK \l "_Toc401432211" 10 Index PAGEREF _Toc401432211 \h 25
1 Introduction
The Password Expiration Date Web Service Protocol enables client applications to query a server to determine the date when a user's password will expire so that the application can warn the user to change the password.
Sections 1.8, 2, and 3 of this specification are normative and can contain the terms MAY, SHOULD, MUST, MUST NOT, and SHOULD NOT as defined in HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=90317" [RFC2119]. Sections 1.5 and 1.9 are also normative but do not contain those terms. All other sections and examples in this specification are informative.
1.1 Glossary
The following terms are defined in [MS-OXGLOS]:
email addressendpointHypertext Transfer Protocol (HTTP)Hypertext Transfer Protocol over Secure Sockets Layer (HTTPS)mailboxSOAPSOAP actionSOAP bodySOAP headerSOAP messageUniform Resource Locator (URL)web serverWeb Services Description Language (WSDL)WSDL messageWSDL port typeXMLXML namespaceXML namespace prefixXML schema
The following terms are specific to this document:
MAY, SHOULD, MUST, SHOULD NOT, MUST NOT: These terms (in all caps) are used as defined in HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=90317" [RFC2119]. All statements of optional behavior use either MAY, SHOULD, or SHOULD NOT.
1.2 References
References to Microsoft Open Specification documents do not include a publishing year because links are to the latest version of the documents, which are updated frequently. References to other documents include a publishing year when one is available.
1.2.1 Normative References
We conduct frequent surveys of the normative references to assure their continued availability. If you have any issue with finding a normative reference, please contact HYPERLINK "mailto:dochelp@microsoft.com" dochelp@microsoft.com. We will assist you in finding the relevant information.
[MS-OXWSCDATA] Microsoft Corporation, " HYPERLINK "[MS-OXWSCDATA].pdf" Common Web Service Data Types".
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997, HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=90317" http://www.rfc-editor.org/rfc/rfc2119.txt
[RFC2616] Fielding, R., Gettys, J., Mogul, J., et al., "Hypertext Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999, HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=90372" http://www.rfc-editor.org/rfc/rfc2616.txt
[RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818, May 2000, HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=90383" http://www.rfc-editor.org/rfc/rfc2818.txt
[RFC3066] Alvestrand, H., "Tags for the Identification of Languages", BCP 47, RFC 3066, January 2001, HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=90404" http://www.ietf.org/rfc/rfc3066.txt
[SOAP1.1] Box, D., Ehnebuske, D., Kakivaya, G., et al., "Simple Object Access Protocol (SOAP) 1.1", May 2000, HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=90520" http://www.w3.org/TR/2000/NOTE-SOAP-20000508/
[WSDL] Christensen, E., Curbera, F., Meredith, G., and Weerawarana, S., "Web Services Description Language (WSDL) 1.1", W3C Note, March 2001, HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=90577" http://www.w3.org/TR/2001/NOTE-wsdl-20010315
[XMLNS] Bray, T., Hollander, D., Layman, A., et al., Eds., "Namespaces in XML 1.0 (Third Edition)", W3C Recommendation, December 2009, HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=191840" http://www.w3.org/TR/2009/REC-xml-names-20091208/
[XMLSCHEMA1] Thompson, H., Beech, D., Maloney, M., and Mendelsohn, N., Eds., "XML Schema Part 1: Structures", W3C Recommendation, May 2001, HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=90608" http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/
[XMLSCHEMA2] Biron, P.V., Ed. and Malhotra, A., Ed., "XML Schema Part 2: Datatypes", W3C Recommendation, May 2001, HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=90610" http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/
1.2.2 Informative References
[MS-OXDSCLI] Microsoft Corporation, " HYPERLINK "[MS-OXDSCLI].pdf" Autodiscover Publishing and Lookup Protocol".
[MS-OXGLOS] Microsoft Corporation, " HYPERLINK "[MS-OXGLOS].pdf" Exchange Server Protocols Master Glossary".
[MS-OXPROTO] Microsoft Corporation, " HYPERLINK "[MS-OXPROTO].pdf" Exchange Server Protocols System Overview".
[MS-OXWSADISC] Microsoft Corporation, " HYPERLINK "[MS-OXWSADISC].pdf" Autodiscover Publishing and Lookup SOAP-Based Web Service Protocol".
1.3 Overview
The Password Expiration Date Web Service Protocol provides an operation that a client application can use to request a user's password expiration date from a server. The application can use this information to present the user with an opportunity to update the password before it expires.
1.4 Relationship to Other Protocols
A client that implements this protocol can use the Autodiscover Publishing and Lookup SOAP-Based Web Service Protocol, as described in HYPERLINK "[MS-OXWSADISC].pdf" [MS-OXWSADISC], or the Autodiscover Publishing and Lookup Protocol, as described in HYPERLINK "[MS-OXDSCLI].pdf" [MS-OXDSCLI], to identify the target HYPERLINK "[MS-OXGLOS].pdf" endpoint (4) to use for each operation.
This protocol uses the SOAP Protocol, as described in HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=90520" [SOAP1.1], to specify the structure information that is exchanged between the client and the server. This protocol uses the XML Protocol, as described in HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=90608" [XMLSCHEMA1] and HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=90610" [XMLSCHEMA2], to describe the message content that is sent to and from the server.
The Password Expiration Date Web Service Protocol uses HYPERLINK "[MS-OXGLOS].pdf" SOAP over HYPERLINK "[MS-OXGLOS].pdf" HTTP, as described in HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=90372" [RFC2616], and SOAP over HYPERLINK "[MS-OXGLOS].pdf" HTTPS, as described in HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=90383" [RFC2818], as shown in the following layering diagram.
Figure 1: This protocol in relation to other protocols
For conceptual background information and overviews of the relationships and interactions between this and other protocols, see HYPERLINK "[MS-OXPROTO].pdf" [MS-OXPROTO].
1.5 Prerequisites/Preconditions
The endpoint (4) HYPERLINK "[MS-OXGLOS].pdf" URL that is returned by either the Autodiscover Publishing Lookup SOAP-Based Web Service Protocol, as described in HYPERLINK "[MS-OXWSADISC].pdf" [MS-OXWSADISC], or the Autodiscover Publishing and Lookup Protocol, as described in HYPERLINK "[MS-OXDSCLI].pdf" [MS-OXDSCLI], is required to form the HTTP request to the HYPERLINK "[MS-OXGLOS].pdf" web server that hosts this protocol. The operation that this protocol defines cannot be accessed unless the correct endpoint (4) is identified in the HTTP web requests that target this protocol.
To get the endpoint (4) URL, the client application needs a valid mail-enabled account to authenticate with the server.
1.6 Applicability Statement
This protocol is applicable to client applications that inform the user about the expiration date of passwords stored on the server.
1.7 Versioning and Capability Negotiation
This document covers versioning issues in the following areas:
S u p p o r t e d T r a n s p o r t s : T h i s p r o t o c o l u s e s S O A P 1 . 1 , a s s p e c i f i e d i n s e c t i o n H Y P E R L I N K \ l " z 8 e 5 8 5 4 f 4 3 b 5 2 4 8 c e b 8 5 0 8 7 4 2 7 c 9 a d a d 8 " 2 . 1 .
P r o t o c o l V e r s i o n s : T h i s p r o t o c o l s p e c i f i e s o n l y o n e H Y P E R L I N K " [ M S - O X G L O S ] . p d f " W S D L p o r t t y p e v e r s i o n . T h e H Y P E R LINK "[MS-OXGLOS].pdf" WSDL version of the request is identified by using the t:RequestServerVersion element, as described in HYPERLINK "[MS-OXWSCDATA].pdf" [MS-OXWSCDATA] section 2.2.3.9, and the version of the server responding to the request is identified by using the t:ServerVersionInfo element, as described in HYPERLINK "[MS-OXWSCDATA].pdf" [MS-OXWSCDATA] section HYPERLINK \l "z40a202458854494ab6cb567447291e64" 2.2.3.10.
S e c u r i t y a n d A u t h e n t i c a t i o n M e t h o d s : T h i s p r o t o c o l r e l i e s o n t h e w e b s e r v e r t h a t i s h o s t i n g i t t o p e r f o r m a u t h e n t i c a t i o n .
L o c a l i z a t i o n : T h i s p r o t o c o l i n c l u d e s t e x t s t r i n g s i n v a r i o u s m e s s a g e s . L o c a l i z a t i o n c o n s i d e r a t i o n s f o r s u c h s t r i n g s a r e s p e c i f i e d i n s e c t i o n H Y P E R L I N K \ l " z 3 b f d 4 d 4 d 9 c 7 d 4 3 e 8 8 5 8 e c e a e 5 4 2 c 8 a b 8 " 3 . 1 . 4 .
C a p a b i l i t y N e g o t i a t i o n : N o n e .
1 . 8 V e n d o r - E x t e n s i b l e F i e l d s
N o n e .
1 . 9 S t a n d a r d s A s s i g n m e n t s
N o n e .
2 M e s s a g e s
I n t h e f o l l o w i n g s e c t i o n s , t h e s c h e m a d e f i n i t i o n m i g h t d i f f e r f r o m the processing rules imposed by the protocol. The WSDL in this specification provides a base description of the protocol. The schema in this specification provides a base description of the message syntax. The text that specifies the WSDL and schema might specify restrictions that reflect actual protocol behavior. For example, the schema definition might allow for an element to be empty, null, or not present but the behavior of the protocol as specified restricts the same elements to being non-empty, not null, or present.
2.1 Transport
The SOAP version supported is SOAP 1.1. For details, see HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=90520" [SOAP1.1].
This protocol relies on the web server that hosts the application to perform authentication. The protocol MUST support HTTP, as specified in HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=90372" [RFC2616].The protocol SHOULD use secure communications by means of HTTPS, as specified in HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=90383" [RFC2818].
2.2 Common Message Syntax
This section contains common definitions that are used by this protocol. The syntax of the definitions uses HYPERLINK "[MS-OXGLOS].pdf" XML schema, as defined in HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=90608" [XMLSCHEMA1] and HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=90610" [XMLSCHEMA2], and Web Services Description Language (WSDL), as defined in HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=90577" [WSDL].
2.2.1 Namespaces
This specification defines and references various HYPERLINK "[MS-OXGLOS].pdf" XML namespaces using the mechanisms specified in HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=191840" [XMLNS]. Although this specification associates a specific HYPERLINK "[MS-OXGLOS].pdf" XML namespace prefix for each XML namespace that is used, the choice of any particular XML namespace prefix is implementation-specific and not significant for interoperability.
PrefixNamespace URIReferencesoaphttp://schemas.xmlsoap.org/wsdl/soap/ HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=90520" [SOAP1.1] tnshttp://schemas.microsoft.com/exchange/services/2006/messagesxshttp://www.w3.org/2001/XMLSchema HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=90608" [XMLSCHEMA1] HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=90610" [XMLSCHEMA2]wsdlhttp://schemas.xmlsoap.org/wsdl/ HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=90577" [WSDL] thttp://schemas.microsoft.com/exchange/services/2006/typesmhttp://schemas.microsoft.com/exchange/services/2006/messages2.2.2 Messages
This specification does not define any common HYPERLINK "[MS-OXGLOS].pdf" WSDL message definitions.
2.2.3 Elements
This specification does not define any common XML schema element definitions.
2.2.4 Complex Types
This specification does not define any common XML schema complex type definitions.
2.2.5 Simple Types
This specification does not define any common XML schema simple type definitions.
2.2.6 Attributes
This specification does not define any common XML schema attribute definitions.
2.2.7 Groups
This specification does not define any common XML schema group definitions.
2.2.8 Attribute Groups
This specification does not define any common XML schema attribute group definitions.
3 Protocol Details
The client side of this protocol is simply a pass-through. That is, no additional timers or other state is required on the client side of this protocol. Calls made by the higher-layer protocol or application are passed directly to the transport, and the results returned by the transport are passed directly back to the higher-layer protocol or application.
3.1 ExchangeServerPortType Server Details
The Password Expiration Date Web Service Protocol defines a single port type that enables clients to retrieve the password expiration date for a HYPERLINK "[MS-OXGLOS].pdf" mailbox account.
3.1.1 Abstract Data Model
This section describes a conceptual model of possible data organization that an implementation maintains to participate in this protocol. The described organization is provided to facilitate the explanation of how the protocol behaves. This document does not mandate that implementations adhere to this model, as long as their external behavior is consistent with that specified in this document.
This protocol is used to retrieve password expiration dates from the server so that client applications can pass this information on to users. Note that the client in each case is not required to maintain the password expiration date. Rather, the client can use this protocol to request the password expiration date whenever it is needed.
3.1.2 Timers
None.
3.1.3 Initialization
None.
3.1.4 Message Processing Events and Sequencing Rules
This protocol includes the operation that is listed and described in the following table.
Operation nameDescriptionGetPasswordExpirationDate Gets the password expiration date for a mailbox account.3.1.4.1 GetPasswordExpirationDate Operation
The GetPasswordExpirationDate operation provides the password expiration date for the mailbox account.
The following is the WSDL port type specification for this operation.
The following is the WSDL binding specification for this operation.
3.1.4.1.1 Messages
The following table summarizes the set of WSDL message definitions that are specific to the GetPasswordExpirationDate operation.
Message nameDescriptionGetPasswordExpirationDateSoapInSpecifies the HYPERLINK "[MS-OXGLOS].pdf" SOAP message that requests the password expiration date.GetPasswordExpirationDateSoapOutSpecifies the SOAP message that is returned by the server in response.3.1.4.1.1.1 GetPasswordExpirationDateSoapIn Message
The GetPasswordExpirationDateSoapIn WSDL message specifies the GetPasswordExpirationDate operation request to return the password expiration date.
The GetPasswordExpirationDateSoapIn WSDL message is the input message for the HYPERLINK "[MS-OXGLOS].pdf" SOAP action http://schemas.microsoft.com/exchange/services/2006/messages/GetPasswordExpirationDate.
The parts of the GetPasswordExpirationDateSoapIn message are listed and described in the following table.
Part nameElement/typeDescriptionrequestm:GetPasswordExpirationDate (section HYPERLINK \l "zcb5792a7e8a9422ea9d5f83fbe0d5332" 3.1.4.1.2.1)Specifies the HYPERLINK "[MS-OXGLOS].pdf" SOAP body of the request containing the information that is required to check the mailbox account password expiration date.MailboxCulturet:MailboxCulture ( HYPERLINK "[MS-OXWSCDATA].pdf" [MS-OXWSCDATA] section 2.2.3.6)Specifies a HYPERLINK "[MS-OXGLOS].pdf" SOAP header that identifies the culture to be used for accessing the mailbox. The cultures are defined in HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=90404" [RFC3066].RequestVersiont:RequestServerVersion ( HYPERLINK "[MS-OXWSCDATA].pdf" [MS-OXWSCDATA] section 2.2.3.9)Specifies a SOAP header that identifies the schema version for the GetPasswordExpirationDate operation request.3.1.4.1.1.2 GetPasswordExpirationDateSoapOut Message
The GetPasswordExpirationDateSoapOut WSDL message specifies the server response to a GetPasswordExpirationDate operation request.
The GetPasswordExpirationDateSoapOut WSDL message is the output message for the SOAP action http://schemas.microsoft.com/exchange/services/2006/messages/GetPasswordExpirationDate.
The parts of the GetPasswordExpirationDateSoapOut WSDL message are listed and described in the following table.
Part nameElement/typeDescriptionGetPasswordExpirationDateResultm:GetPasswordExpirationDateResponse (section HYPERLINK \l "z45b450a3f6d449f899967a882087e368" 3.1.4.1.2.2)Specifies the SOAP body of the response that contains the requested password expiration date.ServerVersiont:ServerVersionInfo ( HYPERLINK "[MS-OXWSCDATA].pdf" [MS-OXWSCDATA] section 2.2.3.10)Specifies a SOAP header that identifies the server version for the response.3.1.4.1.2 Elements
The following table summarizes the XML schema element definitions that are specific to the GetPasswordExpirationDate operation.
Element name DescriptionGetPasswordExpirationDateSpecifies the root element in a GetPasswordExpirationDate operation request.GetPasswordExpirationDateResponseSpecifies the root element in the response to a GetPasswordExpirationDate operation request.3.1.4.1.2.1 m:GetPasswordExpirationDate Element
The GetPasswordExpirationDate element specifies the root element in a GetPasswordExpirationDate operation request.
3.1.4.1.2.2 m:GetPasswordExpirationDateResponse Element
The GetPasswordExpirationDateResponse element specifies the root element in the response to a GetPasswordExpirationDate operation request.
3.1.4.1.3 Complex Types
The following table summarizes the XML schema complex type definitions that are specific to the GetPasswordExpirationDate operation.
Complex type nameDescriptionGetPasswordExpirationDateTypeSpecifies the parameters that are used to obtain the password expiration date.GetPasswordExpirationDateResponseMessageTypeSpecifies the data to be returned in the response.3.1.4.1.3.1 m:GetPasswordExpirationDateType Complex Type
The GetPasswordExpirationDateType complex type specifies the parameters that are used to obtain the password expiration date. The GetPasswordExpirationDateType complex type extends the BaseRequestType complex type, as specified in HYPERLINK "[MS-OXWSCDATA].pdf" [MS-OXWSCDATA] section 2.2.4.15.
The following table lists and describes the child element of the GetPasswordExpirationDateType complex type.
Element nameTypeDescriptionMailboxSmtpAddressxs:string HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=90610" [XMLSCHEMA2]Specifies the HYPERLINK "[MS-OXGLOS].pdf" email address of the mailbox account for which password expiration information will be returned.
If it is present, it MUST appear only once. If it is empty or omitted, the email address of the logged on user is used.3.1.4.1.3.2 m:GetPasswordExpirationDateResponseMessageType
The GetPasswordExpirationDateResponseMessageType complex type specifies the password expiration date information returned in a GetPasswordExpirationDate operation response. The GetPasswordExpirationDateResponseMessageType complex type extends the ResponseMessageType complex type, as specified in HYPERLINK "[MS-OXWSCDATA].pdf" [MS-OXWSCDATA] section 2.2.4.57.
The following table lists and describes the child element of the GetPasswordExpirationDateResponseMessageType complex type.
Element nameTypeDescriptionPasswordExpirationDatexs:dateTime HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=90610" [XMLSCHEMA2]Specifies the password expiration date for a mailbox account.
This element MUST be present, and it MUST appear only once. 3.1.4.1.4 Simple Types
None.
3.1.4.1.5 Attributes
None.
3.1.4.1.6 Groups
None.
3.1.4.1.7 Attribute Groups
None.
3.1.5 Timer Events
None.
3.1.6 Other Local Events
None.
4 Protocol Examples
4.1 GetPasswordExpirationDate Request
The following XML example is a request to the GetPasswordExpirationDate operation, as described in section HYPERLINK \l "zd6b3d7c50bcd4ed883acf0789236d086" 3.1.4.1.
user1@contoso.com
5 Security
5.1 Security Considerations for Implementers
None.
5.2 Index of Security Parameters
None.
6 Appendix A: Full WSDL
The HYPERLINK "[MS-OXGLOS].pdf" XML files that are listed in the following table are required in order to implement the functionality specified in this document.
File nameDescriptionSectionMS-OXWSPED.wsdlContains the WSDL for the implementation of this protocol. HYPERLINK \l "z6da0a4a73f274a778757f5ad1b27ba35" 6MS-OXWSPED-messages.xsdContains the XML schema type definitions that are used in this protocol. HYPERLINK \l "zfacd2f7f082e430ab384dc883eca78b3" 7These files have to be placed in a common folder in order for the WSDL to validate and operate. Also, any schema files that are included in or imported into the MS-OXWSPED-messages.xsd schema have to be placed in the common folder with these files.
This section contains the contents of the MS-OXWSPED.wsdl file.
7 Appendix B: Full XML Schema
For ease of implementation, this section includes the full XML schema for this protocol.
This file has to be placed in a common folder in order for the WSDL to validate and operate.
This schema includes the file listed in the following table. To operate correctly, this file has to be present in the folder that contains the WSDL and schema file for this protocol.
File nameDefining specificationMS-OXWSCDATA-messages.xsd HYPERLINK "[MS-OXWSCDATA].pdf" [MS-OXWSCDATA] section 7.1
8 Appendix C: Product Behavior
The information in this specification is applicable to the following Microsoft products or supplemental software. Refe r e n c e s t o p r o d u c t v e r s i o n s i n c l u d e r e l e a s e d s e r v i c e p a c k s :
M i c r o s o f t E x c h a n g e S e r v e r 2 0 1 0 S e r v i c e P a c k 2 ( S P 2 )
M i c r o s o f t E x c h a n g e S e r v e r 2 0 1 3
E x c e p t i o n s , i f a n y , a r e n o t e d b e l o w . I f a s e r v i c e p a c k o r Q u i c k F i x E n g i n e e r i n g ( Q F E ) n u m b e r a p p e a r s w i t h t h e product version, behavior changed in that service pack or QFE. The new behavior also applies to subsequent service packs of the product unless otherwise specified. If a product edition appears with the product version, behavior is different in that product edition.
Unless otherwise specified, any statement of optional behavior in this specification that is prescribed using the terms SHOULD or SHOULD NOT implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term MAY implies that the product does not follow the prescription.
9 Change Tracking
This section identifies changes that were made to the [MS-OXWSPED] protocol document between the July 2014 and October 2014 releases. Changes are classified as New, Major, Minor, Editorial, or No change.
The revision class New means that a new document is being released.
The revision class Major means that the technical content in the document was significantly revised. Major changes affect protocol interoperab i l i t y o r i m p l e m e n t a t i o n . E x a m p l e s o f m a j o r c h a n g e s a r e :
A d o c u m e n t r e v i s i o n t h a t i n c o r p o r a t e s c h a n g e s t o i n t e r o p e r a b i l i t y r e q u i r e m e n t s o r f u n c t i o n a l i t y .
T h e r e m o v a l o f a d o c u m e n t f r o m t h e d o c u m e n t a t i o n s e t .
T h e r e v i s i o n c l a s s M i n o r m e a n s t h a t t h e m e a n ing of the technical content was clarified. Minor changes do not affect protocol interoperability or implementation. Examples of minor changes are updates to clarify ambiguity at the sentence, paragraph, or table level.
The revision class Editorial means that the formatting in the technical content was changed. Editorial changes apply to grammatical, formatting, and style issues.
The revision class No change means that no new technical changes were introduced. Minor editorial and formatting changes may hav e b e e n m a d e , b u t t h e t e c h n i c a l c o n t e n t o f t h e d o c u m e n t i s i d e n t i c a l t o t h e l a s t r e l e a s e d v e r s i o n .
M a j o r a n d m i n o r c h a n g e s c a n b e d e s c r i b e d f u r t h e r u s i n g t h e f o l l o w i n g c h a n g e t y p e s :
N e w c o n t e n t a d d e d .
C o n t e n t u p d a t e d .
C o n t e n t r e m o v e d .
N e w p r o d u c t b e h a v i o r n o t e a d d e d .
P r o d u c t b e h a v i o r n o t e u p d a t e d .
P r o d u c t b e h a v i o r n o t e r e m o v e d .
N e w p r o t o c o l s y n t a x a d d e d .
P r o t o c o l s y n t a x u p d a t e d .
P r o t o c o l s y n t a x r e m o v e d .
N e w c o n t e n t a d d e d d u e t o p r o t o c o l r e v i s i o n .
C o n t e n t u p d a t e d d u e t o p r o t o c o l r e v i s i o n .
C o n t e n t r e m o v e d d u e t o p r o t o c o l r e v i s i o n .
N e w p r o t o c o l s y n t a x a d d e d d u e t o p r o t o c o l r e v i s i o n .
P r o t o c o l s y n t a x u p d a t e d d u e t o p r o t o c o l r e v i s i o n .
P r o t o c o l s y n t a x r e m o v e d d u e t o p r o t o c o l r e v i s i o n .
O b s o l e t e d o c u m e n t r e m o v e d .
E d i t o r i a l c h a n g e s a r e a l w a y s c l a s s i f i e d w i t h t h e c h a n g e t y p e E d i t o r i a l l y u p d a t e d .
S o m e i m p o r t a n t t e r m s u s e d i n t h e c h a n g e t y p e d e s c r i p t i o n s a r e d e f i n e d a s f o l l o w s :
P r o t o c o l s y n t a x r e f e r s t o d a t a e l e m e n t s ( s u c h a s p a c k e t s , s t r u c t u r e s , e n u m e r a t i o n s , a n d m e t h o d s ) a s w e l l a s i n t e r f a c e s .
P r o t o c o l r e v i s i o n r e f e r s t o c h a n g e s m a d e t o a p r o t o c o l t h a t a f f e c t t h e b i t s t h a t a r e s e n t o v e r t h e w i r e .
T h e c h a n g e s m a d e t o t h i s d o c u m e n t a r e l i s t e d i n t h e f o l l o w i n g t a b l e . F o r m o r e i n f o r m a t i o n , p l e a s e c o n t a c t H Y P E R L I N K " m a i l t o : d o c h e l p @ m i c r o s o ft.com" dochelp@microsoft.com.
SectionTracking number (if applicable) and descriptionMajorchange(Y or N)Change type HYPERLINK \l "zc839c4c0d0dc49a4977d1aa66a6cb80d" 2.2.1 HYPERLINK \l "zc839c4c0d0dc49a4977d1aa66a6cb80d" NamespacesAdded one reference for "http://www.w3.org/2001/XMLSchema".NContent updated.10 Index
A
Abstract data model
HYPERLINK \l "z54f7348bdf4b4b64bb9279dcbd176697" server 11
HYPERLINK \l "zb983b5425da744b392d6a5d07b9291d3" Applicability 7
HYPERLINK \l "z144342a4fafb472284e3d799c17b99ad" Attribute groups 10
HYPERLINK \l "z46711c068614414f9e8df740778ca836" Attributes 10
C
HYPERLINK \l "z2be139d6afed4185988535bd00041eaf" Capability negotiation 7
HYPERLINK \l "z6a4d10204f5044af89fcdd924a44eb3e" Change tracking 23
HYPERLINK \l "z381da4b27b3843e683aa16711a3773ce" Complex types 10
D
Data model - abstract
HYPERLINK \l "z54f7348bdf4b4b64bb9279dcbd176697" server 11
E
Events
HYPERLINK \l "z01a241b7608b4d72bda6b52314ab0905" local - server 16
HYPERLINK \l "z51052097317f4b5e884cacca8c5a656c" timer - server 16
Examples
HYPERLINK \l "z466a0ffa4e10400aaf17fdb6478673e8" GetPasswordExpirationDate request 17
F
HYPERLINK \l "z024dff8f12664ea8b1506e206bcf03a2" Fields - vendor-extensible 8
HYPERLINK \l "z6da0a4a73f274a778757f5ad1b27ba35" Full WSDL 19
HYPERLINK \l "zfacd2f7f082e430ab384dc883eca78b3" Full XML Schema 21
G
HYPERLINK \l "z466a0ffa4e10400aaf17fdb6478673e8" GetPasswordExpirationDate request example 17
HYPERLINK \l "z1b5705773fd0471091c03f21c5f253f0" Glossary 5
HYPERLINK \l "z0607a2a058014f1b9d030301d07b8293" Groups 10
I
HYPERLINK \l "zb0b0d6a3e7794816932ac26b5521e2e4" Implementer - security considerations 18
HYPERLINK \l "ze7d0b47bc8094cf19b83b1bcd61097ba" Index of security parameters 18
HYPERLINK \l "z3d1253623df24543bd146d559c606c2c" Informative references 6
Initialization
HYPERLINK \l "z3f58c959cf7247f194bbc0143c332fc7" server 11
HYPERLINK \l "z2751e011713642dd8971d1258ca33db8" Introduction 5
L
Local events
HYPERLINK \l "z01a241b7608b4d72bda6b52314ab0905" server 16
M
Message processing
HYPERLINK \l "z3bfd4d4d9c7d43e8858eceae542c8ab8" server 11
Messages
HYPERLINK \l "z144342a4fafb472284e3d799c17b99ad" attribute groups 10
HYPERLINK \l "z46711c068614414f9e8df740778ca836" attributes 10
HYPERLINK \l "z381da4b27b3843e683aa16711a3773ce" complex types 10
HYPERLINK \l "z845fa9cd10d0440195ebf2efac321567" elements 9
HYPERLINK \l "z428dc65c62754c1dbc2542d429e49bc0" enumerated 9
HYPERLINK \l "z0607a2a058014f1b9d030301d07b8293" groups 10
HYPERLINK \l "zc839c4c0d0dc49a4977d1aa66a6cb80d" namespaces 9
HYPERLINK \l "z62a01a7fc6584979b17d485eee9a2cb2" simple types 10
HYPERLINK \l "z1c80107f54944bb6baa2affbe44fe54d" syntax 9
HYPERLINK \l "z8e5854f43b5248ceb85087427c9adad8" transport 9
N
HYPERLINK \l "zc839c4c0d0dc49a4977d1aa66a6cb80d" Namespaces 9
HYPERLINK \l "z002b826bb83449fbb3b5ffbdb68de256" Normative references 5
O
Operations
HYPERLINK \l "zd6b3d7c50bcd4ed883acf0789236d086" GetPasswordExpirationDate Operation 11
HYPERLINK \l "z99778e50546d4d3481452a672be2466e" Overview (synopsis) 6
P
HYPERLINK \l "ze7d0b47bc8094cf19b83b1bcd61097ba" Parameters - security index 18
HYPERLINK \l "zd654ac08328441f592dc2b318436fb11" Preconditions 7
HYPERLINK \l "zd654ac08328441f592dc2b318436fb11" Prerequisites 7
HYPERLINK \l "z3eefaa6bc2b340db934a43c83797ffe8" Product behavior 22
Protocol Details
HYPERLINK \l "zb6399e1cfaa742d7961c59fe00170ee1" overview > T _ # 4 }
X Y j k T U | } , B + N O T U V W s t u v *j
hQ h- 0J UmH nH u h- mH nH uhQ h- 0J mH nH u$j hQ h- 0J UmH nH u h- h- 5j h7 h- 0J U
h- 0J j h- U
h- 0Jh h- 8 = > T # } , " + $If gd\ l gd- [ gd- gd- gd- gd- + , 7 , $If gd\ l kd $$If V 4 \
oE#
t ( 0 (#6 4 4
a p( yt- 7 ; ? V W b f 5 kd$ $$If V \
oE#
t 0 (#6 4 4
a p( yt- $If gd\ l f l 5 kd $$If V \
oE#
t 0 (#6 4 4
a p( yt- $If gd\ l g 5 kd $$If V \
oE#
t 0 (#6 4 4
a p( yt- $If gd\ l g h s w } H 5 5 5 5 $If gd\ l kd $$If V \
oE#
t 0 (#6 4 4
a p( yt- H 5 5 5 5 $If gd\ l kdH $$If V \
oE#
t 0 (#6 4 4
a p( yt- $ . { H 5 5 5 5 $If gd\ l kd $$If V \
oE#
t 0 (#6 4 4
a p( yt- { | H 5 5 5 5 $If gd\ l kd $$If V \
oE#
t 0 (#6 4 4
a p( yt- I H 5 5 5 5 $If gd\ l kd $$If V \
oE#
t 0 (#6 4 4
a p( yt- I J U Y _ H 5 5 5 5 $If gd\ l kdl $$If V \
oE#
t 0 (#6 4 4
a p( yt- H 5 5 5 5 $If gd\ l kd5 $$If V \
oE#
t 0 (#6 4 4
a p( yt- 9 H 5 5 5 5 $If gd\ l kd $$If V \
oE#
t 0 (#6 4 4
a p( yt- 9 : ; < N H C > > <