- DHKeyP and DHKeyG
- DHKeyP2048 and DHKeyG2048
The following TDGSS mechanism properties are set as shown in the table for the TDNEGO mechanism and may or may not be modified.
|Do Not Modify These Properties||These Properties May Be Modified|
TDNEGO requires a complete LdapConfig section at the server, if mechanism policy is used as a selection criterion. If you are not using mechanism policy to restrict the mechanisms available for negotiation, the LdapConfig settings are not required.
The NegotiationSupported property is boolean and signifies that a mechanism is actually a pseudo mechanism that negotiates between the client and the server to find an appropriate mechanism to use. All mechanisms that fit this description will have NegotiationSupported set to yes; TDNEGO has this property set to yes. If the mechanism has NegotiationSupported set to yes it must also have at least one NegotiatedMechanism ObjectId set, otherwise an error is reported by the tdgssconfig executable. The NegotiationSupported property should not be modified.
The DefaultNegotiatingMechanism mechanism property is boolean and is similar to the DefaultMechanism property. DefaultNegotiatingMechanism is used to specify a default negotiating mechanism from among those mechanisms whose NegotiationSupported mechanism property is yes. DefaultNegotiatingMechanism is used to determine the default mechanism when both the client and the server support mechanism negotiation. The default setting for DefaultNegotiatingMechanism is no.
If both client and server support negotiation, but no common negotiating mechanism exists between them, the existing DefaultMechanism property is used to select a default mechanism.