CSOAR-3221 : API Error NoRegisteredProviderFound on MS Sentinel Integration #5326
+261
−3
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mahendrak-sumo
requested review from
kimsauce,
jpipkin1,
JV0812,
mafsumo and
amee-sumo
as code owners
mahendrak-sumo
changed the title
|
@mahendrak-sumo, please provide instructions to customers for the fields on the configuration dialog for this integration. I know it's out of scope for this ticket, but from now on when I review PRs for integrations I will ask developers to provide information for the configuration dialog. 
|
Yes @jpipkin1 , I am working on this as par the latest document contents. |
jpipkin1
approved these changes
May 8, 2025
There was a problem hiding this comment.
Approved, @mahendrak-sumo. I made some minor changes (see commit "Updates from review").
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…ration
Purpose of this pull request
The action was failing with an error like no resourcefound error for resource incidents, the issue was with next_link attribute which we got from the response and we were adding the params to it regardless it had the params automatically.
Select the type of change
Ticket (if applicable)