Integration CrowdStrike error OAuth
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-03-2023 06:46 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-22-2023 05:09 PM
@LucasPadula Did you ever figure this out? We set up our connector, worked fine for about a month and then poof. I have tried the fix, nothing works.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-13-2023 10:55 AM
Hi Lucas,
I hope you were able to find a resolution to the issue. I had to rebuild our OAuth Connections and I hope by following the high level steps we took, you can walk through the process and find the failure point. The steps I took to rebuild our OAuth connections were:
- Create the connection or child aliases (sys_alias)
- Create OAuth Entity Profile (oauth_entity)
- Select Connect to a third party OAuth Provider.
- Enter the Client information including the token URL.
- Enter Client Credentials in the Default Grant type field.
- Create OAuth 2.0 Credentials (discovery_credentials)
- Create the HTTP(s) Connection (http_connection)
- Connect the OAuth 2.0 Credentials in the Credential field.
- Connect the Alias in the Connection alias field.
- Enter the Connection URL from the installation guide.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-29-2024 03:15 AM
@LucasPadula the connection url mentioned in the Product document is probably incorrect, as when i used that i got the same error, our CS team shared a different connection url which seemed to work.
