IP access control

Within the scope of a single workspace, you can limit access to a pool of IP addresses. Users trying to access the profile from other addresses are denied.

Checking IP policy

Method reference available here.

Request:

curl --location --request \
GET 'https://{SYNERISE_API_BASE_PATH}/uauth/settings/user-bp-ip-policy' \
--header 'Authorization: Bearer eyJhbGc..._tNS0B28LLHc'

The following response shows that IP access control is disabled.

{
    "enabled": false,
    "enableSupportSubnets": true,
    "ipPolicy": []
}

Updating IP policy

Method reference available here.

The following request enables IP allowlisting, with two addresses allowed. It also allows access from Synerise support subnets. The subnet IPs depend on the configuration.

Important: You must send a complete list of allowed IPs every time - if a list already exists, it is overwritten by the request.
curl --location --request \
POST 'https://{SYNERISE_API_BASE_PATH}/uauth/settings/user-bp-ip-policy' \
--header 'Authorization: Bearer eyJhbGc..._tNS0B28LLHc' \
--header 'Content-Type: application/json' \
--data-raw '{
    "enabled": true,
    "enableSupportSubnets": true,
    "ipPolicy": [
        "192.0.2.12",
        "192.0.2.15"
    ]
}'

The response includes the new settings:

{
    "enabled": true,
    "enableSupportSubnets": true,
    "ipPolicy": [
        "192.0.2.12",
        "192.0.2.15"
    ]
}

😕

We are sorry to hear that

Thank you for helping improve out documentation. If you need help or have any questions, please consider contacting support.

😉

Awesome!

Thank you for helping improve out documentation. If you need help or have any questions, please consider contacting support.

Close modal icon Placeholder alt for modal to satisfy link checker