Red Hat Solution Integration Error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-12-2023 02:31 PM - edited 01-12-2023 02:33 PM
I am getting the following error when the Red Hat Solution Integration runs. This integration has not had any modifications and last ran successfully on January 9.
Error Message: Encountered error running the integration. Error: Invalid response code received from RedHat: 403
Curious if anyone else has seen this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-10-2023 11:07 AM
Hello,
We are also seeing the same error and I wonder if you were able to resolve it.
Thank you!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2024 09:18 AM
Hello Were you able to resolve this issue we are starting to see the integration error out with a 404
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-25-2024 06:21 PM
haha. I came to check and see if anyone else is still having issues and am just responding to my original post now apparently. I am still having intermittent issues. It just really seems as if the integrations for solution management are not that great in general.
Additionally, I finally was able to get the NVD update installed (had to uninstall and reinstall in order to get it to run.) Once the initial run FINALLY completed, it seems fine. I am not completely convinced that adding the API key is actually working though.
I am grateful that my Tenable integrations for the time being are running smoothly.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-26-2024 06:44 AM
We have seen consistent Red Hat integration failures for the past week. Have a ticket open with SN Support and they are requesting addition information. Current work to capture that information.
Related to the NVD integration what we found out was not only adding the API Key but it required getting multiple API keys and try them until it ran. Sometime a many as 3 API Key attempts. We contacted NVD Support they acknowledged the issue and is looking into fixing it. That said when we went to production for 2.0 the first Key we obtained seemed to work.
