Revision Summary Date Revision History Revision Class Comments 12/16/2011 1.0 New Released new document. 3/30/2012 1.0 None No changes to the meaning, language, or formatting of the technical content. 7/12/2012 1.0 None No changes to the meaning, language, or formatting of the technical content. 10/25/2012 1.0 None No changes to the meaning, language, or formatting of the technical content. 1/31/2013 2.0 Major Significantly changed the technical content. 8/8/2013 3.0 Major Significantly changed the technical content. 11/14/2013 4.0 Major Significantly changed the technical content. 2/13/2014 5.0 Major Significantly changed the technical content.
5/15/2014 5.0 None No changes to the meaning, language, or formatting of the technical content. 6/30/2015 6.0 Major Significantly changed the technical content. 10/16/2015 6.0 None No changes to the meaning, language, or formatting of the technical content. 7/14/2016 6.0 None No changes to the meaning, language, or formatting of the technical content. 6/1/2017 6.0 None No changes to the meaning, language, or formatting of the technical content.
Relationship to Other Protocols The Remote Authorization API Protocol is dependent on RPC and TCP for its transport. No other protocol currently depends on the Remote Authorization API Protocol. Prerequisites/Preconditions The Remote Authorization API Protocol is an RPC interface and, as a result, has the prerequisites specified in (section 1.5) as being common to RPC interfaces. It is assumed that a Remote Authorization API Protocol client has obtained the name of a remote computer that supports the Remote Authorization API Protocol before this protocol is invoked. Applicability Statement This protocol is appropriate only for implementing a tool to remotely approximate and profile "what-if" authorization decisions. Versioning and Capability Negotiation This document covers versioning issues in the following areas: Supported Transports: This protocol uses multiple RPC Protocol Sequences as specified in section . Security and Authentication Methods: As specified in section 3.2.1.4.1. Capability Negotiation: The RAZA protocol does not support negotiation of the interface version to use. Instead, an implementation needs to be configured with the interface version to use. Vendor Extensible Fields This protocol cannot be extended by any party other than Microsoft. This protocol uses Win32 error codes as defined in section 2.2. Vendors SHOULD reuse those values with their indicated meaning. Choosing any other value runs the risk of a collision in the future. Standards Assignments The following table lists the value for the authzr interface specified in section . Parameter Value Reference UUID for authzr
Appendix B: Product Behavior The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include released service packs. The "earlier" and "later", when used with a product version, refer to either all preceding versions or all subsequent versions, respectively. The term "through" refers to the inclusive range of versions. Applicable Microsoft products are listed chronologically in this section. Windows Client Windows 8 operating system Windows 8.1 operating system Windows 10 operating system Windows Server Windows Server 2012 operating system Windows Server 2012 R2 operating system Windows Server 2016 operating system Exceptions, if any, are noted below. If a service pack or Quick Fix Engineering (QFE) number appears with the 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. <1> Section 1.3: The RAZA client role is implemented on Windows 8 and later operating products configured to run in a Windows domain environment. The RAZA server role is implemented on Windows Server 2012 and later and is operating when the Windows Server operating system is configured to run in a Windows domain environment. <2> Section 5.1: In Windows, this access is controlled by membership in the Windows Authorization Access