# Connector Auth Validation

### Feature Introduction <a href="#feature-introduction" id="feature-introduction"></a>

The automatic Connector Auth validation feature automatically checks whether the credentials for a Connector Auth are correct or not during the creation of a it:

<figure><img src="/files/O6x19ZouVvny27DjFwUg" alt=""><figcaption><p>Example of an error from "More Details"</p></figcaption></figure>

The user can view the error message returned by the API, update the credentials and try again, or choose to save the Connector Auth despite the error by clicking the **Save Regardless** button.

To enable this functionality, the endpoint must be specified in the Authentication Configuration of the corresponding connector.

{% hint style="info" %}
As the authentication process for OAuth2 and refreshable token implicitly check whether the credentials are correct, the explicit validation does not have to and cannot be used with them.
{% endhint %}

### Configuration on connector

<figure><img src="/files/56znqkVzlreegquT5K1O" alt=""><figcaption><p>Edit Connector > Auth Configuration</p></figcaption></figure>

In the Authentication Configuration, a new field called `test_endpoint` needs to be added, which specifies the endpoint.

This endpoint is the same as in a regular action, so the base domain should not be specified.

This (currently) needs to be a `GET` endpoint to keep the configuration as simple as possible and to prevent accidental creation of anything in the customer’s account.

When the user adds a connector auth, we send a request to that endpoint with the user’s credentials and, if specified, their base domain.

{% hint style="info" %}
For Helpers, we need to code the validation in the backend. As of now, we’ve only seen a use case for validation in the FTP and SQL Helpers (this just checks the connection—kind of like a ping to the respective server), but this can be expanded if it makes sense.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.locoia.com/connectors/building-connectors/base-connector-setup/connector-auth-validation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.