Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
2.7.10
-
Unknown
Description
When using WS-Security and org.apache.ws.security.validate.JAASUsernameTokenValidator, the later populates org.apache.ws.security.validate.Credential with a javax.security.auth.Subject received from JAAS. It then propagates to WSSecurityEngineResult (TAG_SUBJECT). UsernameTokenInterceptor ignores that and instead uses createSubject method, which is always null.
The workaround currently is to force using WSS4JInInterceptor, which precedes UsernameTokenInterceptor and handles subject information correctly.