3.1.4 Message Processing Events and Sequencing Rules
This section specifies the methods for this protocol, in addition to their processing rules.<21><22>
This protocol contains some methods with parameters that have no effect on message processing in any environment. These are called out as "ignored".
Note This protocol shares an interface with the Local Security Authority (Domain Policy) Remote Protocol, as specified in [MS-LSAD].
Methods in RPC Opnum Order
|
Method |
Description |
|---|---|
|
Frees the resources held by a context handle. Opnum: 0 |
|
|
Opnum1NotUsedOnWire |
Opnum: 1 |
|
Lsar_LSA_DP_2 |
Opnum: 2 |
|
Lsar_LSA_DP_3 |
Opnum: 3 |
|
Lsar_LSA_DP_4 |
Opnum: 4 |
|
Opnum5NotUsedOnWire |
Opnum: 5 |
|
Opens a context handle to the RPC server. Opnum: 6 |
|
|
Lsar_LSA_DP_7 |
Opnum: 7 |
|
Lsar_LSA_DP_8 |
Opnum: 8 |
|
Opnum9NotUsedOnWire |
Opnum: 9 |
|
Lsar_LSA_DP_10 |
Opnum: 10 |
|
Lsar_LSA_DP_11 |
Opnum: 11 |
|
Lsar_LSA_DP_12 |
Opnum: 12 |
|
Lsar_LSA_DP_13 |
Opnum: 13 |
|
Translates a batch of security principal names. For information on selecting which version to use, see section 3. Opnum: 14 |
|
|
Translates a batch of security principal SIDs. For information on selecting which version to use, see section 3. Opnum: 15 |
|
|
Lsar_LSA_DP_16 |
Opnum: 16 |
|
Lsar_LSA_DP_17 |
Opnum: 17 |
|
Lsar_LSA_DP_18 |
Opnum: 18 |
|
Lsar_LSA_DP_19 |
Opnum: 19 |
|
Lsar_LSA_DP_20 |
Opnum: 20 |
|
Opnum21NotUsedOnWire |
Opnum: 21 |
|
Opnum22NotUsedOnWire |
Opnum: 22 |
|
Lsar_LSA_DP_23 |
Opnum: 23 |
|
Lsar_LSA_DP_24 |
Opnum: 24 |
|
Lsar_LSA_DP_25 |
Opnum: 25 |
|
Lsar_LSA_DP_26 |
Opnum: 26 |
|
Lsar_LSA_DP_27 |
Opnum: 27 |
|
Lsar_LSA_DP_28 |
Opnum: 28 |
|
Lsar_LSA_DP_29 |
Opnum: 29 |
|
Lsar_LSA_DP_30 |
Opnum: 30 |
|
Lsar_LSA_DP_31 |
Opnum: 31 |
|
Lsar_LSA_DP_32 |
Opnum: 32 |
|
Lsar_LSA_DP_33 |
Opnum: 33 |
|
Lsar_LSA_DP_34 |
Opnum: 34 |
|
Lsar_LSA_DP_35 |
Opnum: 35 |
|
Lsar_LSA_DP_36 |
Opnum: 36 |
|
Lsar_LSA_DP_37 |
Opnum: 37 |
|
Lsar_LSA_DP_38 |
Opnum: 38 |
|
Lsar_LSA_DP_39 |
Opnum: 39 |
|
Lsar_LSA_DP_40 |
Opnum: 40 |
|
Lsar_LSA_DP_41 |
Opnum: 41 |
|
Lsar_LSA_DP_42 |
Opnum: 42 |
|
Lsar_LSA_DP_43 |
Opnum: 43 |
|
Opens a context handle to the RPC server. Opnum: 44 |
|
|
Returns the name and the domain name of a security principal. Opnum: 45 |
|
|
Lsar_LSA_DP_46 |
Opnum: 46 |
|
Lsar_LSA_DP_47 |
Opnum: 47 |
|
Lsar_LSA_DP_48 |
Opnum: 48 |
|
Lsar_LSA_DP_49 |
Opnum: 49 |
|
Lsar_LSA_DP_50 |
Opnum: 50 |
|
Lsar_LSA_DP_51 |
Opnum: 51 |
|
Opnum52NotUsedOnWire |
Opnum: 52 |
|
Lsar_LSA_DP_53 |
Opnum: 53 |
|
Lsar_LSA_DP_54 |
Opnum: 54 |
|
Lsar_LSA_DP_55 |
Opnum: 55 |
|
Opnum56NotUsedOnWire |
Opnum: 56 |
|
Translates a batch of security principal SIDs. For information on selecting which version to use, see section 3. Opnum: 57 |
|
|
Translates a batch of security principal names. For information on selecting which version to use, see section 3. Opnum: 58 |
|
|
Lsar_LSA_DP_59 |
Opnum: 59 |
|
Opnum60NotUsedOnWire |
Opnum: 60 |
|
Opnum61NotUsedOnWire |
Opnum: 61 |
|
Opnum62NotUsedOnWire |
Opnum: 62 |
|
Opnum63NotUsedOnWire |
Opnum: 63 |
|
Opnum64NotUsedOnWire |
Opnum: 64 |
|
Opnum65NotUsedOnWire |
Opnum: 65 |
|
Opnum66NotUsedOnWire |
Opnum: 66 |
|
Opnum67NotUsedOnWire |
Opnum: 67 |
|
Translates a batch of security principal names. For information on selecting which version to use, see section 3. Opnum: 68 |
|
|
Opnum69NotUsedOnWire |
Opnum: 69 |
|
Opnum70NotUsedOnWire |
Opnum: 70 |
|
Opnum71NotUsedOnWire |
Opnum: 71 |
|
Opnum72NotUsedOnWire |
Opnum: 72 |
|
Lsar_LSA_DP_73 |
Opnum: 73 |
|
Lsar_LSA_DP_74 |
Opnum: 74 |
|
Opnum75NotUsedOnWire |
Opnum: 75 |
|
LsarLookupSids3 |
Translates a batch of security principal SIDs. For information on selecting which version to use, see section 3. Opnum: 76 |
|
Translates a batch of security principal names. For information on selecting which version to use, see section 3. Opnum: 77 |
Note Gaps in the opnum numbering sequence represent opnums of methods that are documented in [MS-LSAD], or opnums that MUST NOT<23> be used over the wire.
No exceptions SHOULD be thrown beyond those thrown by the underlying RPC protocol [MS-RPCE].
The return values of all methods MUST conform to the specification of NTSTATUS, as specified in [MS-ERREF] section 2.3. Specific return values for normative processing conditions are specified in this document in the subsections of this section.
Unless otherwise specified, all negative values returned by an implementation are treated equivalently by the client as a message processing error. Unless otherwise specified, all non-negative values returned by an implementation are treated equivalently by the client as a success (of message processing).
Return values for implementation-specific conditions are left to the implementer's discretion, subject to the constraints specified in [MS-ERREF]. For example, an implementation can re-use an existing value in [MS-ERREF], such as 0xC0000017 (no memory).
The RPC methods shown in the following sections are organized in the following order:
Methods that allow a client to open and close a connection.
Methods that translate given names to SIDs.
Methods that translate SIDs to names.