You are viewing a plain text version of this content. The canonical link for it is here.
Posted to rampart-dev@ws.apache.org by "Sumit Shah (JIRA)" <ji...@apache.org> on 2008/12/11 17:47:44 UTC
[jira] Created: (RAMPART-206) RampartUtil.getToken() not setting
parent properties on the STS service call resulting in HTTP 401 error
RampartUtil.getToken() not setting parent properties on the STS service call resulting in HTTP 401 error
--------------------------------------------------------------------------------------------------------
Key: RAMPART-206
URL: https://issues.apache.org/jira/browse/RAMPART-206
Project: Rampart
Issue Type: Bug
Components: rampart-core, rampart-integration, rampart-trust
Affects Versions: 1.4
Environment: Windows
Reporter: Sumit Shah
Assignee: Ruchith Udayanga Fernando
Priority: Critical
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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (RAMPART-206) RampartUtil.getToken() not setting
parent properties on the STS service call resulting in HTTP 401 error
Posted by "Sumit Shah (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAMPART-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12656055#action_12656055 ]
Sumit Shah commented on RAMPART-206:
------------------------------------
I have fixed this issue locally. I am also attaching the source file. Please let me know if you want me to check in to the SVN stream.
- Sumit
> RampartUtil.getToken() not setting parent properties on the STS service call resulting in HTTP 401 error
> --------------------------------------------------------------------------------------------------------
>
> Key: RAMPART-206
> URL: https://issues.apache.org/jira/browse/RAMPART-206
> Project: Rampart
> Issue Type: Bug
> Components: rampart-core, rampart-integration, rampart-trust
> Affects Versions: 1.4
> Environment: Windows
> Reporter: Sumit Shah
> Assignee: Ruchith Udayanga Fernando
> Priority: Critical
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (RAMPART-206) RampartUtil.getToken() not setting
parent properties on the STS service call resulting in HTTP 401 error
Posted by "Nandana Mihindukulasooriya (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAMPART-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nandana Mihindukulasooriya reassigned RAMPART-206:
--------------------------------------------------
Assignee: Nandana Mihindukulasooriya (was: Ruchith Udayanga Fernando)
> RampartUtil.getToken() not setting parent properties on the STS service call resulting in HTTP 401 error
> --------------------------------------------------------------------------------------------------------
>
> Key: RAMPART-206
> URL: https://issues.apache.org/jira/browse/RAMPART-206
> Project: Rampart
> Issue Type: Bug
> Components: rampart-core, rampart-integration, rampart-trust
> Affects Versions: 1.4
> Environment: Windows
> Reporter: Sumit Shah
> Assignee: Nandana Mihindukulasooriya
> Priority: Critical
> Attachments: RampartUtil.java
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (RAMPART-206) RampartUtil.getToken() not setting
parent properties on the STS service call resulting in HTTP 401 error
Posted by "Nandana Mihindukulasooriya (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAMPART-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12720032#action_12720032 ]
Nandana Mihindukulasooriya commented on RAMPART-206:
----------------------------------------------------
Fixed in the trunk.
thanks,
Nandana
> RampartUtil.getToken() not setting parent properties on the STS service call resulting in HTTP 401 error
> --------------------------------------------------------------------------------------------------------
>
> Key: RAMPART-206
> URL: https://issues.apache.org/jira/browse/RAMPART-206
> Project: Rampart
> Issue Type: Bug
> Components: rampart-core, rampart-integration, rampart-trust
> Affects Versions: 1.4
> Environment: Windows
> Reporter: Sumit Shah
> Assignee: Nandana Mihindukulasooriya
> Priority: Critical
> Attachments: RampartUtil.java
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (RAMPART-206) RampartUtil.getToken() not setting
parent properties on the STS service call resulting in HTTP 401 error
Posted by "Sumit Shah (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAMPART-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sumit Shah updated RAMPART-206:
-------------------------------
Attachment: RampartUtil.java
I have fixed the issue. Please review.
-Sumit
> RampartUtil.getToken() not setting parent properties on the STS service call resulting in HTTP 401 error
> --------------------------------------------------------------------------------------------------------
>
> Key: RAMPART-206
> URL: https://issues.apache.org/jira/browse/RAMPART-206
> Project: Rampart
> Issue Type: Bug
> Components: rampart-core, rampart-integration, rampart-trust
> Affects Versions: 1.4
> Environment: Windows
> Reporter: Sumit Shah
> Assignee: Ruchith Udayanga Fernando
> Priority: Critical
> Attachments: RampartUtil.java
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.