Authentication
Clients and Endpoints authenticate to Connect API with an API token and the Endpoint name so that Connect knows who is making requests and what permissions you have.
If you are using the Connect API through the Java API provided by Connect Plugin then you do not write authentication code.
Required Headers
All requests to the Connect API require the following headers:
Connect-Endpoint- The name of the endpoint the token belongs to.Authorization: Bearer <ENDPOINT_TOKEN>- The token of the endpoint you are connecting to.
Endpoint Names
Connect has the concept of globally unique endpoint names to identify your server even after restarts. The Connectors use a token file to authenticate that you own an endpoint name in the Connect Network.
{"token":"T-ozinikukmabrpyzogjjl"}The token and endpoint name have a direct relationship. Keep your token.json file safe, or import the endpoint into the Connect Dashboard so you can reset the token later.
If you lose token.json for an endpoint that was not imported into the dashboard, Connect cannot immediately prove that the endpoint name still belongs to you. The endpoint name stays reserved while the connector keeps refreshing it, and for a reclaimable period after its last successful refresh.
Currently, an unimported endpoint name becomes reclaimable after it has not been refreshed for more than 30 days and no active endpoint session is still using it. Before that period has passed, a connector with a different token will be rejected because the endpoint name is still reserved.
Super Endpoints
Checkout Super Endpoints guide for authorizing other endpoints to act on your Endpoint's behalf.