Authentication methods

Authenticated IPs

Instead of sending username and password credentials with every request, trusted IPs can be authenticated by adding them to your account's allow list, and any request coming from those authenticated IPs does not need to include a username or password.

It's important to be cautious with which IPs you authenticate. If a shared IP (such as an AWS shared IP) is authenticated, it's possible your account will be used by other parties through the shared IP.

Requests from authenticated IPs don't include credentials, and instead use a custom port to target a particular pipeline. You can define each pipeline's port range (between 9000 and 10000) when creating or modifying it. If the example request below were sent from an authenticated IP, its target port (9400) would be used to identify the relevant pipeline.

curl -x

Geotargeting and Session settings

Because requests from authenticated IPs do not include a username portion, geotargeting and session parameters are set on the pipeline level only.

You can create/modify your pipelines in one of two ways:

To learn more about working with authenticated IPs and managing pipelines, see the Backconnect Gateway Authentication methods page.