Liberty 19.0.0.3. There is an issue with mapDistributedIdentities (as reported TS002526035)

z/Os Connect 3.0.0.22 and Liberty 19.0.0.3.

There is an issue with mapDistributedIdentities (as reported TS002526035) in which assumes the signon request is a distributed identity when in fact it is a SAF identity. This incorrect assumption produces numerous error messages and is confusing as to whether there is a problem or not, particularly after any server recycle.

You cannot configure ZCEE to allow use of both Basic Auth from a browser and OpenIdConnectClient using JWT and RACMAP to authenticate connections without producing FFDC errors if the server is recycled.

1. User authenticates to ZCEE using RACF user/password from browser (REST client). At this point an LTPA token is returned with the response.
2. ZCEE server is recycled.
3. User sends another request containing the LTPA token.
4. ZCEE (Liberty) tries to map the identity in the token to a RACF ID. This mapping failure is reported in an error message and FFDC.
5. After the mapping error, ZCEE seems to assume that the identity must be a RACF ID, SSO authentication succeeds and the request is processed normally.

It seems that all propagation logins (token login) are going through the RACMAP check and rejected if not found.

[10/11/18 18:10:22:859 BST] 00000038 com.ibm.ws.logging.internal.impl.IncidentImpl
I FFDC1015I: An FFDC Incident has been created: "com.ibm.ws.security.saf.SAFException: CWWKS2905E: SAF service IRRSIA00_CREATE did not succeed because user null was not found in the SAF registry. SAF return code 0x00000008. RACF return code 0x00000008. RACF reason code 0x00000010. com.ibm.ws.security.credentials.saf.internal. SAFCredentialsServiceImpl 932" at ffdc_18.10.11_18.10.22.0.log

[10/11/18 18:10:22:889 BST] 00000038 com.ibm.ws.logging.internal.impl.IncidentImpl
I FFDC1015I: An FFDC Incident has been created: "javax.security.auth.login.CredentialException: could not create SAF credential for abcdef com.ibm.ws.security.authentication.jaas.modules.TokenLoginModule 116" at ffdc_18.10.11_18.10.22.1.log

[10/11/18 18:10:22:903 BST] 00000038 com.ibm.ws.security.registry.saf.internal.SAFRegistry
I CWWKS2932I: The authorized version of the SAF user registry is activated. Authentication will proceed using authorized native services.

and the following in the JobLog
18.10.22 STC38064 ICH408I USER(ZCONAS ) GROUP(ZCONAGR ) NAME
(ZOSCONNECTA SRV ID ) 672
672 DISTRIBUTED IDENTITY IS NOT DEFINED:
672 X<73>X<70>X<79>X<61>X<6A>X<63>
X<7A>X<6F>X<73>X<43>X<6F>X<6E>X<6E>X<6
672 5>X<63>X<74>

Liberty should be modified to resolve this incorrect behaviour in mapDistributedIdentities to allow Basic Auth from a browser (which is sending in an LTPA token) and OpenidConnectClient to co-exist without producing misleading error messages after a server recyle.