Query API worked in UAT, 403 in Production

Options

We're currently migrating from an on premises instance of FE7 to FE NXT. In the process we were given access to an UAT environment. I built a process that retrieves information from AR using the Query API.

This process is working in the UAT environment, but failing in the production environment. In the production environment I'm receiving responses that are zero bytes long with a 403 status code. The failed request show up on the SKY API Analytics page as “Blocked requests”.

I notice that AR is available in web view in our UAT environment but not in the production environment. Could it be that our production environment is an older version of FE NXT in which the Query API is not fully available?

I think I've gone through all of the necessary steps to connect and authorize my SKI API application to the production environment. Is there something else I should look for?

Comments

  • Erik Leaver
    Erik Leaver ✭✭✭✭✭
    Ancient Membership Facilitator 2 Name Dropper Photogenic

    @Aaron Spike You likely need your system admin to add rights for you for AR. One of those rights should be access to query:

    c6729ba2dc3557afd5b5f43c7b615e19-huge-im
  • @Erik Leaver I’m the admin. Can you tell me how to find this screen?

  • Erik Leaver
    Erik Leaver ✭✭✭✭✭
    Ancient Membership Facilitator 2 Name Dropper Photogenic

    @Aaron Spike Should be under Control Panel → Security → Role Management → AR Roles

  • @Erik Leaver, here's what we see in our UAT environment:

    test perms.png

    And here's what we see in production:

    prod perms.png

    The list of available roles is quite different. Is there something that we need to change at a higher level?

  • Erik Leaver
    Erik Leaver ✭✭✭✭✭
    Ancient Membership Facilitator 2 Name Dropper Photogenic

    @Aaron Spike Images are broken :-(. I'd reach out to your implementation team and ask why the permissions are different between the two environments. I'd guess your user account doesn't have the same permissions enabled in prod that are currently enabled in test.

  • @Erik Leaver, Thanks! We have reached out but haven't heard back yet.

  • @Erik Leaver The implementation team “pushed modern permissions” and this solved the issue. Thanks!

Categories