Skip to content

IP Location Activation - API #201

Open

Description

@zaraki12345

Hello!

Referring to your email from October 3, 2019:
"To further improve security, we are enabling the IP Location Activation feature for all Pardot accounts on Monday, October 14, 2019."

"At this time, the enablement of this feature is limited to human users only and will not impact API authentication."

I've tested this function for my account:
image
"Enable IP Security: enabled"

When I enabled this function my API integrations stop to work... All forms are no longer displayed on website...

Are you sure this feature not impact the API integrations?

Activity

  1. adelawalla commented on Oct 7, 2019

    @adelawalla
    Contributor

    @zaraki12345 It's a little bit deceiving. The automatic enablement that took place exempted the API. However, if the user manually changes the setting, it becomes enabled for all users in all contexts.

  2. zaraki12345 commented on Oct 8, 2019

    @zaraki12345
    Author

    Isn't that bug? Upcoming update IP Location Activation (14 october 2019) say's: "At this time, the enablement of this feature is limited to human users only"

  3. adelawalla commented on Oct 8, 2019

    @adelawalla
    Contributor

    @zaraki12345 My understanding is that there are two groups of accounts:

    • One set of accounts were forcibly enabled on 14 October. These accounts have an API exemption in place to avoid breaking API integrations.
    • Another set of accounts was not forcibly enabled on 14 October, due to the fact that these accounts already had the feature enabled. For these accounts, the functionality works as documented, where IP Security applies to both the UI and the API.

    Your account likely falls into the second group. If you believe there's a bug, please feel free to contact the support team.

  4. adelawalla commented on Oct 9, 2019

    @adelawalla
    Contributor

    @zaraki12345 I found out there is a workaround. You can use IP Whitelisting to avoid having to activate your IP address over the API.

  5. zaraki12345 commented on Oct 10, 2019

    @zaraki12345
    Author

    So you are guessing that there is two group of accounts... I'm in contact with support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions