Set Up API and Macro Security Dialog Box

From this dialog box, you can enable the Reflection .NET API, and specify the API channel type and corresponding settings.

Note: If you need to use the API in multiple instances of Reflection simultaneously, use layouts. You can specify different settings for the IPC channel name and API port for each layout in the Layout Settings dialog box.

API Settings*


Disable API	Select to prevent custom applications from accessing this installation of Reflection.
Use IPC	Select to allow custom applications access to the API via the IPC (Inter-Process Communication) channel. Specify the name in the IPC channel name box.
Use TCP/IP	Select to allow custom applications access the API via the TCP/IP channel. Caution: If you select this option, select Secure access to reduce your security risk.
	API port	Specify the port (number) to use.
	Allow remote access	Select to allow custom applications running on other computers to access the API. Caution: If you select this option, select Secure Access to reduce your security risk.
	Secure Access	Select to encrypt, sign, and authenticate information that is exchanged between a custom application and the API when using TCP/IP. When selected, you can specify the credential to use for authentication. Select Authenticate using domain credential to secure access to the API using your domain credential (anyone who has an account on that domain can access the Reflection API). Select Authenticate using local credential (the user name and password for your local Windows account) to control access by administering accounts on your computer. A benefit of this option is that you can work with the API in a non-domain environment.
Legacy API preference	Use this setting to determine if Reflection legacy macros are supported, and to determine which legacy API has preference for the GetObject() method used to retrieve API COM objects. Reflection supports multiple APIs, but can accept GetObject() calls for only one type of legacy API object at a time.
	Select	If you
	No Legacy API	Don't use legacy Reflection macros, or if your code doesn't use GetObject() to access legacy API COM objects.
	Reflection	Use legacy Reflection macros, or if you use GetObject() to access legacy Reflection API COM objects. Each session document that you subsequently open or create has legacy macro capability; it includes a legacy VBA project in addition to the standard VBA project in the Visual Basic Editor. Note: Legacy API support is provided in all Reflection settings files that you open in the workspace (including settings files saved as Reflection session documents), regardless of this setting.
	EXTRA!	Use GetObject() to access legacy EXTRA! API COM objects.

Action Permissions

Specify what you want to happen if an action that has been restricted through Group Policy or the Permissions Manager is initiated through a macro or API call.

Require elevated rights on Vista; do not execute on XP

On a computer running Windows Vista, select to control restricted actions with User Account Control (UAC).

-or-

On a computer running Windows XP, select to prevent restricted actions from running.

Execute the action

Select to run restricted actions that are initiated through a macro or API call as expected. The same actions won't run if they are initiated through the user interface.