Symptom
We have sometimes found that on Curator Systems that don't have Internet access, logging into Curator Gateway is a slow process, at times taking over one minute to log in.
Resolution
There are a few things that can be applied to the setup to get around this problem.
On investigation of this issue, usually the cause is that Gateway is trying to connect out to the Internet for various reasons which causes timeouts, and the login attempt (onscreen at least) doesn't complete until those timeouts have passed.
Access 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 means that the local machine will no longer check on 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 to 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"
]
},
And the above can be changed to this to disable these calls:
"HubSpot": {
"ApiKey": "04a8a077-f503-4e21-aa91-709f1a806890",
"AddOrUpdateContactEventTypes": [
]
},