Cannot turn "Require Authentication" for Profile API in Sandbox | Community
Skip to main content
DmytroPanchenk
New Participant
November 23, 2023
Solved

Cannot turn "Require Authentication" for Profile API in Sandbox

  • November 23, 2023
  • 1 reply
  • 843 views

Hi,

I am trying to turn on "Require Authentication" for Profile API in a Sandbox Target account.

When I do that in the UI, it displays "Invalid Payload" error message, and I see the following response in the debugger:

 

{ "errors": [ { "message": "Invalid payload", "locations": [ { "line": 2, "column": 3 } ], "path": [ "updateClientSettings" ], "extensions": { "code": "BAD_USER_INPUT" } } ], "data": { "updateClientSettings": null } }

 

 When I try to do the same using the API, I get the following response:

 

{ "httpStatus": 400, "requestId": "7VnWWIH0UnSEqkmaakiMLCy6VYzJDg2Y", "requestTime": "2023-11-23T03:02:36.836118Z", "errors": [ { "errorCode": "NotReadable.Json", "message": "Invalid Json. Unrecognized property name 'mobileDeviceTargetingEnabled'. Location: line - 1, column - 261.", "meta": {} } ] }

 

 The response is the same no matter whether I include mobileDeviceTargetingEnabled in the request JSON or not.

Could you please suggest how to overcome that problem? Is it possible to turn on the authentication for Profile API in a Sandbox at all?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by alexbishop

I've had confirmation this is a known bug, reported last week; a solution is being worked on currently but I don't have a date on when the fix will be deployed yet

1 reply

alexbishop
Employee
November 23, 2023

I've checked across several different accounts and I see the same error message, so it looks like there is a wider issue. I've asked internally if there is any additional information on this but I would recommend raising a ticket with Client Care if you haven't already done so

alexbishop
alexbishopAccepted solution
Employee
November 24, 2023

I've had confirmation this is a known bug, reported last week; a solution is being worked on currently but I don't have a date on when the fix will be deployed yet