WebService Realms stop working after modification of (External) Applications

Version Affected:  22.12+

Description:  
After modifying an External Application (SAML/OIDC etc) in New Experience, Web Service calls fail to work as expected until the FBA WebService has been disabled and enabled again on the affected Realm

Cause:  
This is a known bug which affects (External) Applications  (this does not affect Internal Applications)

Workaround:
FBA WebService credentials will persist during this operation
In the New Experience Admin Console
 - Edit the affected Realm and scroll to the bottom of the screen
 - Edit the 'FBA Web Service' section
 - Disable FBA Web Service and Save the change
 - Enable FBA Web Service and Save the change

Resolution:  
This has been logged as a Bug in EE-3818
A fix has been released in 24.4.7.5 and above, please contact SecureAuth Support for assistance in upgrading
 

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.