axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Reinhold (JIRA)" <>
Subject [jira] [Created] (RAMPART-392) Rampart unable to insert security token into security header
Date Sun, 23 Sep 2012 11:42:07 GMT
Brian Reinhold created RAMPART-392:

             Summary: Rampart unable to insert security token into security header
                 Key: RAMPART-392
             Project: Rampart
          Issue Type: Bug
          Components: rampart-core
    Affects Versions: 1.6.2
         Environment: Windows 7, jre, jdk 6 or 7, Eclipse client, Tomcat Axis2/Rampart for
both STS service and 'myCommunicate' service. Axis2 1.6.2, Axiom 1.2.13 OR 1.2.14 Snapshot
sept 21, 2012.
NOTE this is 1.6.2 it DOES exist but the bug infrastructure says it doesn't.
            Reporter: Brian Reinhold
            Priority: Critical
             Fix For: 1.6.2

When attempting to add the security token obtained from the default STS service, and 'unexpected
end of document' exception is thrown. Stack trace follows:

Unexpected END_DOCUMENT Unexpected END_DOCUMENT event
	at org.apache.rampart.util.RampartUtil.appendChildToSecHeader(
	at org.apache.rampart.util.RampartUtil.insertSiblingAfter(
	at org.apache.rampart.builder.BindingBuilder.handleSupportingTokens(
	at org.apache.rampart.handler.RampartSender.invoke(
	at org.apache.axis2.engine.Phase.invokeHandler(
	at org.apache.axis2.engine.Phase.invoke(
	at org.apache.axis2.engine.AxisEngine.invoke(
	at org.apache.axis2.engine.AxisEngine.send(
	at org.apache.axis2.description.OutInAxisOperationClient.send(
	at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(
	at org.apache.axis2.client.OperationClient.execute(

There was no problem when using Axis2 1.5.1 and Rampart 1.5.1 and Axiom 1.2.9. The problem
shows up on the client side when moving to versions 1.6.2 and axiom 1.2.14 to solve server
side bugs with respect to SAML.  See JIRA AXIOM-439

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message