Resolution

There are a few changes that can be made to the setup to get around this problem.

On investigation of this issue, we have found that usually the cause is that Gateway is trying to connect to the Internet for various reasons which causes timeouts, and the login attempt (on screen at least) doesn't complete until those timeouts have passed.

To fix this issue, go to your Internet Options on the affected machine. From the Advanced tab, disable the following options:

• Check for publisher's certificate revocation
• Check for server's certificate revocation
• Check for signatures on downloaded programs

Disabling these options stops the local machine from checking the Internet for certificate statuses. This may help with performance on the local machine.

When it comes to the server, an adjustment can be made in the appsettings.json file within the Curator Gateway installation directory to disable our API calls to Hubspot. The following is the default configuration:

"HubSpot": {
    "ApiKey": "04a8a077-f503-4e21-aa91-709f1a806890",
    "AddOrUpdateContactEventTypes": [
      "SignUp",
      "Register",
      "Login",
      "Activated",
      "Deactivated"
    ]
  },

"HubSpot": {
    "ApiKey": "04a8a077-f503-4e21-aa91-709f1a806890",
    "AddOrUpdateContactEventTypes": [
    ]
  },