Fixes are available
17.0.0.2: WebSphere Application Server Liberty 17.0.0.2
17.0.0.3: WebSphere Application Server Liberty 17.0.0.3
17.0.0.4: WebSphere Application Server Liberty 17.0.0.4
18.0.0.1: WebSphere Application Server Liberty 18.0.0.1
18.0.0.2: WebSphere Application Server Liberty 18.0.0.2
18.0.0.3: WebSphere Application Server Liberty 18.0.0.3
18.0.0.4: WebSphere Application Server Liberty 18.0.0.4
19.0.0.1: WebSphere Application Server Liberty 19.0.0.1
19.0.0.2: WebSphere Application Server Liberty 19.0.0.2
19.0.0.3: WebSphere Application Server Liberty 19.0.0.3
19.0.0.4: WebSphere Application Server Liberty 19.0.0.4
19.0.0.5: WebSphere Application Server Liberty 19.0.0.5
19.0.0.6: WebSphere Application Server Liberty 19.0.0.6
19.0.0.7: WebSphere Application Server Liberty 19.0.0.7
19.0.0.8: WebSphere Application Server Liberty 19.0.0.8
19.0.0.9: WebSphere Application Server Liberty 19.0.0.9
19.0.0.10: WebSphere Application Server Liberty 19.0.0.10
19.0.0.11: WebSphere Application Server Liberty 19.0.0.11
19.0.0.12: WebSphere Application Server Liberty 19.0.0.12
20.0.0.1: WebSphere Application Server Liberty 20.0.0.1
20.0.0.2: WebSphere Application Server Liberty 20.0.0.2
20.0.0.3: WebSphere Application Server Liberty 20.0.0.3
20.0.0.4: WebSphere Application Server Liberty 20.0.0.4
20.0.0.5: WebSphere Application Server Liberty 20.0.0.5
20.0.0.6: WebSphere Application Server Liberty 20.0.0.6
20.0.0.7: WebSphere Application Server Liberty 20.0.0.7
20.0.0.8: WebSphere Application Server Liberty 20.0.0.8
20.0.0.9: WebSphere Application Server Liberty 20.0.0.9
20.0.0.10: WebSphere Application Server Liberty 20.0.0.10
20.0.0.11: WebSphere Application Server Liberty 20.0.0.11
20.0.0.12: WebSphere Application Server Liberty 20.0.0.12
21.0.0.3: WebSphere Application Server Liberty 21.0.0.3
21.0.0.4: WebSphere Application Server Liberty 21.0.0.4
21.0.0.5: WebSphere Application Server Liberty 21.0.0.5
21.0.0.6: WebSphere Application Server Liberty 21.0.0.6
21.0.0.7: WebSphere Application Server Liberty 21.0.0.7
21.0.0.8: WebSphere Application Server Liberty 21.0.0.8
21.0.0.9: WebSphere Application Server Liberty 21.0.0.9
21.0.0.1: WebSphere Application Server Liberty 21.0.0.1
21.0.0.2: WebSphere Application Server Liberty 21.0.0.2
21.0.0.10: WebSphere Application Server Liberty 21.0.0.10
21.0.0.11: WebSphere Application Server Liberty 21.0.0.11
21.0.0.12: WebSphere Application Server Liberty 21.0.0.12
22.0.0.1: WebSphere Application Server Liberty 22.0.0.1
22.0.0.2: WebSphere Application Server Liberty 22.0.0.2
22.0.0.3: WebSphere Application Server Liberty 22.0.0.3
22.0.0.4: WebSphere Application Server Liberty 22.0.0.4
APAR status
Closed as program error.
Error description
When searching for a domain user <username>/<domain> the slash character causes an exception in basicRegistry: PatternSyntaxException: Illegal/unsupported escape sequence near index This causes all further registry searches to fail, even if the allowOpIfRepoDown option is set.
Local fix
need fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server Liberty- Virtual Member Manager * * (VMM) * **************************************************************** * PROBLEM DESCRIPTION: UserRegistry implementations that throw * * RuntimeExceptions can cause Federated * * Repository failures * **************************************************************** * RECOMMENDATION: * **************************************************************** Customer has both an LDAP registry and utilizing the BasicRegistry. A java.util.regex.PatternSyntaxException occurs when searching using a principal name in the form of realm\username. This RuntimeException is uncaught in Federated Repositories causing select UserRegistry calls to fail. This will occur even if the configuration is set to allow operations if repositories are down. For the example above, the following failures may be seen: Caused by: java.util.regex.PatternSyntaxException: Illegal/unsupported escape sequence near index 12 MYDOMAIN001\MYUSER ^ at java.util.regex.Pattern.error(Pattern.java:1966) at java.util.regex.Pattern.escape(Pattern.java:2482) at java.util.regex.Pattern.atom(Pattern.java:2209) at java.util.regex.Pattern.sequence(Pattern.java:2141) at java.util.regex.Pattern.expr(Pattern.java:2007) at java.util.regex.Pattern.compile(Pattern.java:1707) at java.util.regex.Pattern.<init>(Pattern.java:1362) at java.util.regex.Pattern.compile(Pattern.java:1039) at java.util.regex.Pattern.matches(Pattern.java:1144) at java.lang.String.matches(String.java:1907) at com.ibm.ws.security.registry.basic.internal.BasicRegistry.search Map(BasicRegistry.java:445) at com.ibm.ws.security.registry.basic.internal.BasicRegistry.getUse rs(BasicRegistry.java:387) at com.ibm.ws.security.wim.RepositoryManager.getFederationUREntityT ype(RepositoryManager.java:896) at com.ibm.ws.security.wim.ProfileManager.getImpl(ProfileManager.ja va:335) at com.ibm.ws.security.wim.ProfileManager.genericProfileManagerMeth od(ProfileManager.java:260) at com.ibm.ws.security.wim.ProfileManager.get(ProfileManager.java:2 17) at com.ibm.ws.security.wim.VMMService.get(VMMService.java:218) at com.ibm.ws.security.wim.registry.util.BridgeUtils.getEntityByIde ntifier(BridgeUtils.java:462) at com.ibm.ws.security.wim.registry.util.UniqueIdBridge.getUniqueUs erId(UniqueIdBridge.java:170) at com.ibm.ws.security.wim.registry.WIMUserRegistry.getUserSecurity Name(WIMUserRegistry.java:311) ... 55 more
Problem conclusion
The Federated Repositories code was updated to handle all exception types. The fix for this APAR is currently targeted for inclusion in fix pack 17.0.0.2. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PI78192
Reported component name
WAS LIBERTY COR
Reported component ID
5725L2900
Reported release
CD0
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-03-14
Closed date
2017-05-11
Last modified date
2017-05-11
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WAS LIBERTY COR
Fixed component ID
5725L2900
Applicable component levels
RCD0 PSY
UP
Document Information
Modified date:
04 May 2022