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
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
%5BMS-RAA%5D-170601.docx