Bryan Brouckaert created JBWS-3498: -------------------------------------- Summary: Service implementations fail when a SAML-assertion is present in the request. Key: JBWS-3498 URL: https://issues.jboss.org/browse/JBWS-3498 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: ws-security Affects Versions: jbossws-cxf-4.0.2 Reporter: Bryan Brouckaert I have a service that requires X509 endorsing supporting token, but also SAML supporting token although that mustn't be processed. Apparently wss4j processes it anway, but can't because it is missing the OpenSAML module. The result is the same if the SAML supporting token is or not in the WS-SecurityPolicy. It seems that the saml module should be part of the JBossWS. This isn't a request to implement the SAML Token Profile of ticket JBWS-491, just to add SAML module to activate the SAML support of wss4j. In JBoss 6,1 this basic SAML support of wss4j was working pritty wel. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira