Bug: WebService Calls Stop Working After Modifying an External Application

Version Affected: 22.12 - 24.4.7.4
Bug Number: EE-3818
Bug Status: Closed - Fixed
Fixed in Version(s): 24.4.7.5 and later

 

Overview

After modifying an External Application (SAML, OIDC, etc.) in the New Experience Admin Console, WebService calls on realms using that Application stop working as expected.

 

Cause

This is a known defect that affects External Applications specifically -- Internal Applications are not affected.

 

Resolution / Workaround

This was fixed in IdP 24.4.7.5 and later. Contact SecureAuth Support for help upgrading if your environment is on an earlier version.

If you cannot upgrade immediately, disabling and re-enabling the affected realm's FBA Web Service restores it without needing to re-enter its credentials, since they persist across the toggle:

1. In the New Experience Admin Console, edit the affected realm and scroll to the FBA Web Service section.
2. Disable FBA Web Service and save the change.
3. Enable FBA Web Service and save the change.

SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.