Federated SAF registries can incorrectly claim a SAF user or group is not in the realm when calling UserRegistry.isValidGroup

[jvanhill]

Describe the bug
Calling UserRegistry.isValidGroup when using federatedRegistry-1.0 can result in a CWIML0515E error message that claims the <GROUP> is not in the scope of the <REALM>, when in fact it is.

com.ibm.ws.security.registry.RegistryException: CWIML0515E: The user registry operation could not be completed. The <GROUP> entity is not in the scope of the <REALM> realm. Specify an entity that is in the scope of the configured realm in the server.xml file.
        at com.ibm.ws.security.wim.registry.util.ValidBridge.isValidGroup(ValidBridge.java:215)
        at com.ibm.ws.security.wim.registry.WIMUserRegistry.isValidGroup(WIMUserRegistry.java:455)
        at com.ibm.ws.security.registry.internal.UserRegistryWrapper.isValidGroup(UserRegistryWrapper.java:231)
        ...

Steps to Reproduce
Federate a SAF registry and call the UserRegistry.isValidGroup method with a group that is in the SAF registry.

Expected behavior
The UserRegistry.isValidGroup call should return true instead of an exception.

Diagnostic information:

• OpenLiberty Version: Any
• Affected feature(s): federatedRegistry-1.0, zosSecurity-1.0 (WebSphere Liberty only)
• Java Version: Any

Additional context
None.