Referring to the recent post about the January KB articles, which experienced a slight delay, I’m thrilled to share our February articles with you. Stay tuned, as the latest March articles will be coming your way soon!
This post contains all new KB (Solution) articles published in February and any articles with significant updates. The article summary provides an overview of the article’s purpose.
-
502 Bad Gateway and Connection was closed errors when using standalone IG (All versions)
The purpose of this article is to provide assistance if you encounter a 502 Bad Gateway response when routing from IG (standalone mode) to a backend appliction, custom endpoint, or an endpoint in Identity Cloud, AM or IDM using a ReverseProxyHandler. This response is accompanied by a “Connection was closed” error, and in some cases, you may see “Stream was closed” errors.
-
502 Bad Gateway or SocketTimeoutException when using IG 7.x in web container mode
The purpose of this article is to provide assistance if you encounter a 502 Bad Gateway response when routing from IG (web container mode) to a custom endpoint, or an endpoint in Identity Cloud, AM or IDM using a ReverseProxyHandler. This response is accompanied by a “java.net.SocketTimeoutException: null” error. -
SSO login to Identity Cloud fails with an Unable to process unsuccessful response error
The purpose of this article is to provide assistance if you receive a login failure when authenticating to ForgeRock Identity Cloud with SSO and an “Unable to process unsuccessful response: [Status: 401 Unauthorized]” error appears in the logs. -
Admin and end user UIs not accessible with Unexpected failure while serving resource error in IDM (All versions)
The purpose of this article is to provide assistance if the IDM admin and end user UIs are not accessible in IDM. You will see “Unexpected failure while serving resource” with “java.lang.ClassCastException” errors in the logs when this happens. This issue only occurs when Dynatrace® OneAgent® is running. -
Routes with a CORS filter are not deployed after upgrading IG (All versions)
The purpose of this article is to provide assistance if one or more routes with a Cross-origin resource sharing (CORS) filter are not deployed after upgrading IG. The error you see in the logs will depend on whether you have upgraded to IG 2023.11 or later, or an earlier version. -
Errors occur when migrating data with existing links from IDM 6.5.x to IDM 7.3 or 7.4
The purpose of this article is to provide assistance when “Object Class Violation” errors occur when migrating data from IDM 6.5.x to IDM 7.3 or later, and the data you are migrating has links to connected objects.
Additional Resources
Identity Cloud
Documentation
Knowledge Base
Community
Identity Management (IDM)
Documentation
Identity Gateway(IG)
Documentation
Knowledge Base