[RAMPART-206] RampartUtil.getToken() not setting parent properties on the STS service call resulting in HTTP 401 error

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.4
• Component/s: rampart-core, rampart-integration, rampart-trust
• Environment: Windows
• Assignee: Nandana Mihindukulasooriya
• Reporter: Sumit Shah
• Created: 11/Dec/08 16:46
• Updated: 21/Dec/10 09:10
• Resolved: 21/Dec/10 09:10

Description

I have deployed my service in Weblogic 10. I am using Rampart and Rahas to send a Secure Conversation request. The RampartUtil and the STSClient make a service call to the STS service, but the RampartUtil.getToken() fails to set the ServiceClient options of the original service call.

The way I found this is I kept getting HTTP 401 from the server even though I had set the Authenticator on the ServiceClient options while making my business service call. When I debugged, theRampartUtil.getToken() method call did not set the HTTP authenticator options on the STSClient.

The RampartUtil.getToken() at the very least should copy the Authenticator from the parent call to the STS call.