Connection security and troubleshooting

Good practice

• use a dedicated account or integration when the platform allows;
• grant only the permissions indicated in the form;
• Never place a secret in a conversation;
• remove any exposed key immediately;
• remove the access of former employees;
• test a reading after a secret rotation or reconnection.

Check a complete connection

1. Check that the card displays Connect.
2. Open Settings if the connector offers and check the account, site or property ID.
3. Ask for an impact-free reading operation.
4. Compare its result with the original platform.

The badge confirms the registration of access. The test also confirms permissions and perimeter.

Frequent problems

Invalid identifiers

Symptom: refused connection or authentication error at the first test.

Symptom: recreate the secret, copy it without additional space and replace the value in ELChat.

Insufficient permissions

Symptom: some readings work, but a specific action fails.

Solution: compare the rights with the connector sheet and check the account’s access to the targeted resource.

##Aggreek##Aggrefits an empty account or wrong login# is an incorrect connectionSympte or wrong login

**Solution:**check the authorized account and the value recorded in Settings.

###Threat expired or revoked

**Symptom:**status Threat expiredor error 401.

**Solution:**reconnect. If necessary, revoke the previous authorisation on the platform before starting again.

###API limit reached

Symptom: error 429 or unavailability after many calls.

Solution: wait for quota reset and check supplier limits.

Window blocked or closed

Symptom: Google button does not launch anything, or the route stops.

Solution: Allow pop-up windows for ELChat and then restart the connection without closing the window before the result.