Open jvanhill opened 3 years ago
I talked with @arkarkala and he mentioned that appSecurity-3.0/4.0 was built to include the EE8 security-1.0 feature that relies on much of JASPIC, so the startup message is expected.
He did agree, however, that the addition of the JASPIC servlet filters should not result in an FFDC being emitted for a 404 response.
NOTE: This was found while adding support for EE9, and hasn't been merged at the time of writing this defect. To reproduce it in EE8 the server.xml files need be updated to run with appSecurity-3.0 and jaxrs-3.1.
The FAT test
com.ibm.ws.security.openidconnect.client.fat.IBM.OidcClientBasicTests.OidcClientBadAuthorizeEndpointWebContainerError
emits FFDC when running with appSecurity-3.0 (EE8) or with appSecurity-4.0 (EE9).It appears that for some reason a portion of JASPIC starts up and injects its filter and that changes the flow through the filter chain resulting in an FFDC.
We also see the following appear in the log files, though the JASPIC / Jakarta Authentication features are neither listed in the server.xml or listed as being started in the server:
FFDC for EE8 below: