Hi all, I set up the endpoint url for the third party (Twilio) correctly with all of the IDs necessary (client id, secret, and bot id), but I still get an unauthorized error when cURLing the endpoint as well as it not accessing my bot. I've tried adding access policies to make it work but still get unauthorized:

{
  "resourceType": "OperationOutcome",
  "id": "unauthorized",
  "issue": [
    {
      "severity": "error",
      "code": "login",
      "details": {
        "text": "Unauthorized"
      }
    }
  ],
  "extension": [
    {
      "url": "https://medplum.com/fhir/StructureDefinition/tracing",
      "extension": [
        {
          "url": "requestId",
          "valueId": "4dd888d2-0291-4dff-b84e-d9923d44973b"
        },
        {
          "url": "traceId",
          "valueId": "7d7c6093-3e3f-4638-b652-151913831b30"
        }
      ]
    }
  ]
}

For some added context, I am able to get auth credentials when I curl the oauth2 token url. So the client id and secret do work to auth into my medplum app

curl -X POST https://api.kips.health/oauth2/token \

cc: @Deleted User

thanks for the info @rahul1! Any idea why that fix was reverted? was there an issue with it?

That's right, we were seeing some intended behavior in Medplum App, so we're going to have to take another pass