CrowdStrike OAuth2 API token not refreshing

Describe the problem/error/question

When using the built-in CrowdStrike OAuth2 API credentials, a failed HTTP Request to the API (HTTP response code 401) does not get automatically result in an OAuth2 token refresh.

If I open the credential within n8n and wait for the “Connection tested successfully” message, it works again. I have confirmed that in the CrowdStrike API request audit, no token refresh is taking place until I manually open the credential within n8n and test it.

What is the error message (if any)?

The API return with the 401 HTTP error code and the message “access denied, invalid bearer token”.

Please share your workflow

Share the output returned by the last node

{
  "body": {
    "meta": {
      "query_time": 2.39e-7,
      "powered_by": "crowdstrike-api-gateway",
      "trace_id": "7efe427d-6a01-4561-8ff6-5653228becd6"
    },
    "errors": [
      {
        "code": 401,
        "message": "access denied, invalid bearer token"
      }
    ]
  },
  "headers": {
    "server": "nginx",
    "date": "Wed, 13 Dec 2023 11:10:30 GMT",
    "content-type": "application/json",
    "content-length": "231",
    "connection": "close",
    "x-content-type-options": "nosniff",
    "x-cs-traceid": "7efe427d-6a01-4561-8ff6-5653228becd6",
    "x-ratelimit-limit": "15",
    "x-ratelimit-remaining": "13",
    "strict-transport-security": "max-age=31536000; includeSubDomains"
  },
  "statusCode": 401,
  "statusMessage": "Unauthorized"
}

Information on your n8n setup

  • n8n version: 1.18.2
  • Database (default: SQLite): SQLite
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: Ubuntu
1 Like

Hey @tyrells,

Welcome to the community :raised_hands:

I have just created NODE-996 as the internal bug ticket to look into this, Thanks for letting us know.

Also affected by this issue
Just updated to 1.25.1 today and confirmed still occuring