This topic has not yet been rated - Rate this topic

7 Change Tracking

This section identifies changes that were made to the [MS-XOAUTH] protocol document between the October 2012 and February 2013 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 interoperability or implementation. Examples of major changes are:

A document revision that incorporates changes to interoperability requirements or functionality.
An extensive rewrite, addition, or deletion of major portions of content.
The removal of a document from the documentation set.
Changes made for template compliance.

The revision class Minor means that the meaning 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 language and 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 or language changes were introduced. The technical content of the document is identical to the last released version, but minor editorial and formatting changes, as well as updates to the header and footer information, and to the revision summary, may have been made.

Major and minor changes can be described further using the following change types:

New content added.
Content updated.
Content removed.
New product behavior note added.
Product behavior note updated.
Product behavior note removed.
New protocol syntax added.
Protocol syntax updated.
Protocol syntax removed.
New content added due to protocol revision.
Content updated due to protocol revision.
Content removed due to protocol revision.
New protocol syntax added due to protocol revision.
Protocol syntax updated due to protocol revision.
Protocol syntax removed due to protocol revision.
New content added for template compliance.
Content updated for template compliance.
Content removed for template compliance.
Obsolete document removed.

Editorial changes are always classified with the change type Editorially updated.

Some important terms used in the change type descriptions are defined as follows:

Protocol syntax refers to data elements (such as packets, structures, enumerations, and methods) as well as interfaces.
Protocol revision refers to changes made to a protocol that affect the bits that are sent over the wire.

The changes made to this document are listed in the following table. For more information, please contact protocol@microsoft.com.

Section	Tracking number (if applicable) and description	Major change (Y or N)	Change type
1.2.1 Normative References	Removed the references [XMLNS], [XMLSCHEMA1], and [XMLSCHEMA2].	Y	Content updated.
1.2.1 Normative References	Added the reference [MS-OAUTH2EX].	Y	Content updated.
1.2.1 Normative References	Moved the reference [MS-SPS2SAUTH] to Informative References.	Y	Content updated.
1.2.2 Informative References	Moved the reference [MS-SPS2SAUTH] from Normative References.	Y	Content updated.
1.4 Relationship to Other Protocols	Changed reference from [MS-SPS2SAUTH] to [MS-OAUTH2EX].	N	Content updated.
2.2 Message Syntax	Moved claim descriptions from the Abstract Data Model section of the Client Details section.	N	Content updated for template compliance.
2.2 Message Syntax	Changed reference from [MS-SPS2SAUTH] to [MS-OAUTH2EX].	Y	Content updated.
3.1 Client Details	Changed section title from Common Details to Client Details.	N	Content updated for template compliance.
3.1.1 Abstract Data Model	Moved claim descriptions to the Message Syntax section.	N	Content updated for template compliance.
3.1.5.1 Realm Autodiscovery Through HTTP 401 Challenge	Added section for information moved from the Realm Autodiscovery Through HTTP 401 section Challenge in the Server Details section about how the client uses realm autodiscovery.	N	Content updated for template compliance.
3.1.5.1 Realm Autodiscovery Through HTTP 401 Challenge	Clarified the usage of realm autodiscovery.	N	Content updated.
3.1.5.2 Server-to-Server Security Token Contents	Added section for the information moved from the Server-to-Server Security Token Contents section in the Server Details section about the server-to-server security token that the client sends.	N	Content updated for template compliance.
3.1.5.2 Server-to-Server Security Token Contents	Changed reference for server-to-server security token format from [MS-SPS2SAUTH] to [MS-OAUTH2EX].	Y	Content updated.
3.2.5.1 Authentication Within a Single Organization	Added reference for definitions of resource and realm parameters.	Y	New content added.
3.2.5.1 Authentication Within a Single Organization	Changed reference for server-to-server authentication protocol from [MS-SPS2SAUTH] to [MS-OAUTH2EX].	Y	Content updated.
3.2.5.2 Authentication with User Information Within a Single Organization	Added reference for definition of resource and realm parameters.	Y	New content added.
3.2.5.2 Authentication with User Information Within a Single Organization	Changed reference for server-to-server authentication protocol from [MS-SPS2SAUTH] to [MS-OAUTH2EX].	Y	Content updated.
3.2.5.4 Realm Autodiscovery Through HTTP 401 Challenge	Moved specification of how client uses realm autodiscovery to the Realm Autodiscovery Through HTTP 401 Challenge section of the Client Details section.	N	Content updated for template compliance.
3.2.5.5 Server-to-Server Security Token Contents	Moved specification of the server-to-server security token that the client sends to the Server-to-Server Security Token Contents section of the Client Details section.	N	Content updated for template compliance.

Did you find this helpful? Yes No

Not accurate

Not enough depth

Need more code examples

(1500 characters remaining)