Share via


AlwaysUseMessageAuthenticator Property of the IFPCRadiusServer Interface

The AlwaysUseMessageAuthenticator property gets or sets a Boolean value that indicates whether a message authenticator based on the shared secret is to be sent with every message sent to the RADIUS server.

C++

HRESULT put_AlwaysUseMessageAuthenticator(
    VARIANT_BOOL fUseAuthenticator
);
HRESULT get_AlwaysUseMessageAuthenticator(
    VARIANT_BOOL* pfUseAuthenticator
);

Parameters

  • fUseAuthenticator
    Boolean value that specifies whether a message authenticator is to be sent with every message sent to the RADIUS server.

  • pfUseAuthenticator
    Pointer to a Boolean variable that is set on return to VARIANT_TRUE if a message authenticator is to be sent with every RADIUS request, or to VARIANT_FALSE if no message authenticator is to be sent with a RADIUS request.

Return Value

These property methods return S_OK if the call is successful; otherwise, they return an error code.

Visual Basic

Property AlwaysUseMessageAuthenticator As Boolean

Property Value

Boolean value that specifies whether a message authenticator is to be sent with every message sent to the RADIUS server.

Remarks

This property is read/write. Its default value is False (VARIANT_FALSE in C++).

A message authenticator is a digital signature based on the shared secret. Extensible Authentication Protocol (EAP) messages are always sent with a digital signature.

This property must be set to True (VARIANT_TRUE in C++) if the RADIUS server is a Windows 2000 computer running Internet Authentication Service (IAS) and the RADIUS client that is configured for this server has the Client must always send the signature attribute in the request option selected.

Requirements

Client Requires Windows 7 or Windows Vista.
Server Requires Windows Server 2008 R2 or Windows Server 2008 x64 Edition with SP2.
Version Requires Forefront Threat Management Gateway (TMG) 2010.
IDL

Declared in Msfpccom.idl.

DLL

Requires Msfpccom.dll.

See Also

FPCRadiusServer

Send comments about this topic to Microsoft

Build date: 6/30/2010