It can’t – the Login Agent does not accept inbound connections

The configuration file for Login Agent can be manually updated to instruct it to specify the SSLCert switch when it starts

Login Agent automatically enforces encrypted communication

The connection to the Blue Prism Server should be set to use a WCF mode that provides Encryption

Review the message across all tabs within appropriate profile via BPServer.exe

Review the device Windows Application Event Logs

Review the server status panel in Control Room

Use a configured Blue Prism process to interrogate each connected server in turn

Review messages when starting the service manually using BPServer.exe

Use BPDiagnostics to start out a Server Diagnostics and Repair task

Not Applicable – This setting does not exist

When the Interactive Client will only be used for controlling and monitoring a Blue Prism environment (rather than running automations locally)

When the Interactive Client will be used to run automations locally

It should always be disabled for all environments

Each Application Server must connect to a different database

Each Application Server must be configured with the same encryption schemes and identical key

The master application server must be turned on first

All application servers must be configured to enable schedules in order for scheduling to work correctly

When using the in-product Create Database functionality select to create a database that will use Blue Prism single sign-on

After using the in-product Create Database functionality, use the Configure Database functionality to configure it for single sign-on

Use SQL Management Studio, use the CreateScript that is specific to SSO environments to create the database

Using SQL Management Studio create a database, manually run the CreateScript provided by BluePrism, then use the in-product “Configure Database” functionality

As part of the installation, Blue Prism automatically configures the Runtime Resource to start when the device is logged in

Use a scheduled task to start a Blue Prism Runtime Resource with appropriate parameters

Use a policy login script to start a Blue Prism Runtime Resource with appropriate parameters

Put an appropriate batch (*.bat) in the appropriate Start-up Programs folder

It can’t. Once Login Agent has logged a device in, a conventional Runtime Resource must be started and be appropriately instructed to carry out further processing

This is configured within the process that instructs the device to orchestrate a login through use of a wait stage

This is configured within the process that instructs the device to orchestrate a login through use of a navigate stage

This is configured within the business object that instructs the device to orchestrate a login through use of a wait stage

Use the /SSLCert switch in the Runtime Resource start up parameters

Under System - > Settings, enable the “Require secure resource connections” setting

Within the configuration for the Blue Prism Server select a Connection Mode that does not contain the text “insecure”

All of the above

Implement firewall rules to prevent unexpected devices from establishing a connection with the Application Server

Under System - > Settings, enable the “Prevent registration of new Resources” setting

All of the above

All work queue items are automatically encrypted using the most cryptographically strong scheme that has been configured within the environment

Only Work Queue Items associated with Work Queues that have been associated with an Encryption Scheme will be encrypted

Work Queue Items will be encrypted using the algorithm and key on the Encryption Scheme associated with the Work Queue

Work Queue items will be encrypted using the algorithm on the Encryption Scheme associated with the Work

Queue and a key that is randomly generated when the Application Server restarts

Work Queue items cannot be encrypted