Hello team,
We have a credential created to communicate between n8n and Crowdstrike.
I’ve seen that the tickets Crowdstike oauth2 and CrowdStrike OAuth2 API token not refreshing are opened on the same topic.
We currently run [email protected], do you have any solution for this in the current version?
However, I must mention that our workflows in n8n are not impacted by the error, the requests work as expected.
It looks like your topic is missing some important information. Could you provide the following if applicable.
Hey @GabCo,
What does it say under more details? Both of the posts you have linked are due to different caues the first was down to our refresh implemention being incorrect and the second was down to the wrong URL being used.
For the credential check we call the user-management API which your API token may not have been given permission for which would explain why the workflows are running.
Hi @Jon,
Thank you for the fast reply!
Under more details it is written: Forbidden - see attached screenshot.
Where should I find the user-management API, is it under Crowdstrike API?
Thank you!
Hey @GabCo,
Yeah it should be a scope within Crowdstrike.
Hello @Jon
Thanks! However when I go to CRWD API what I can see under scopes is:
Hi @Jon,
This is now solved, I needed the proper role assigned in CRWD to make changes.
Thank you for the hint! Very useful 
Gabriela
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
