The ValidateServerCertificateCRLInForward property gets or sets a Boolean value that indicates whether the Forefront TMG Web proxy will validate server certificates against the relevant certificate revocation list (CRL) in the forward proxy scenario. The setting stored in this property is applicable when the Forefront TMG computer, acting as a Web proxy, opens a secure connection (SSL bridging) to an upstream proxy server or Web server.
HRESULT put_ValidateServerCertificateCRLInForward( VARIANT_BOOL fValidateServerCertificateCRLInForward ); HRESULT get_ValidateServerCertificateCRLInForward( VARIANT_BOOL* pfValidateServerCertificateCRLInForward );
Pointer to a Boolean variable that is set on return to VARIANT_TRUE if the Web proxy will validate server certificates against the relevant CRL in the forward proxy scenario, or to VARIANT_FALSE if the Web proxy will not validate server certificates against the relevant CRL in the forward proxy scenario.
Boolean value that specifies whether the Web proxy will validate server certificates against the relevant CRL in the forward proxy scenario.
These property methods return S_OK if the call is successful; otherwise, they return an error code.
Property ValidateServerCertificateCRLInForward
Boolean value that specifies whether the Web proxy will validate server certificates against the relevant CRL in the forward proxy scenario.
This property is read/write. Its default value is True (VARIANT_TRUE in C++).
After the value of this property has been modified, the change must be written to persistent storage by calling the Save method, and the Microsoft Firewall service must be restarted for the change to take effect. For more information about restarting the Firewall service to apply changes, see Restarting Services After Configuration Changes.
Client | Requires Windows Vista or Windows XP. |
---|---|
Server | Requires Windows Server 2008. |
Version | Requires Forefront Threat Management Gateway (TMG). |
IDL |
Declared in Msfpccom.idl. |
DLL |
Requires Msfpccom.dll. |
Send comments about this topic to Microsoft
Build date: 11/30/2009
© 2008 Microsoft Corporation. All rights reserved.