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 "Keith Godwin Chapman (JIRA)" <ji...@apache.org> on 2008/07/15 07:31:32 UTC
[jira] Created: (RAMPART-186) Password call back not copied over
when the call back is set via a parameter to the axis Service (Secure
conversation)
Password call back not copied over when the call back is set via a parameter to the axis Service (Secure conversation)
----------------------------------------------------------------------------------------------------------------------
Key: RAMPART-186
URL: https://issues.apache.org/jira/browse/RAMPART-186
Project: Rampart
Issue Type: Bug
Reporter: Keith Godwin Chapman
Assignee: Ruchith Udayanga Fernando
I'm implementing security scenarios in the WSO2 Mashup Server (This will allow users to access secure services using JavaScript).
I set the password call back on the client as follows,
axisService.addParameter(WSHandlerConstants.PW_CALLBACK_REF, new PasswordCallbackHandler(authorName));
But unfortunatly rampart does not copy this over when making the request to obtain the token.
Caused by: org.apache.rampart.RampartException: Password CallbackHandler not specified in rampart configuration policy or the CallbackHandler instance not available in the MessageContext
at org.apache.rampart.builder.BindingBuilder.getSignatureBuider(BindingBuilder.java:266)
at org.apache.rampart.builder.AsymmetricBindingBuilder.doSignature(AsymmetricBindingBuilder.java:626)
at org.apache.rampart.builder.AsymmetricBindingBuilder.doSignBeforeEncrypt(AsymmetricBindingBuilder.java:413)
at org.apache.rampart.builder.AsymmetricBindingBuilder.build(AsymmetricBindingBuilder.java:93)
at org.apache.rampart.MessageBuilder.build(MessageBuilder.java:147)
at org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:64)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (RAMPART-186) Password call back not copied over
when the call back is set via a parameter to the axis Service (Secure
conversation)
Posted by "Nandana Mihindukulasooriya (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAMPART-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nandana Mihindukulasooriya reassigned RAMPART-186:
--------------------------------------------------
Assignee: Nandana Mihindukulasooriya (was: Ruchith Udayanga Fernando)
> Password call back not copied over when the call back is set via a parameter to the axis Service (Secure conversation)
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: RAMPART-186
> URL: https://issues.apache.org/jira/browse/RAMPART-186
> Project: Rampart
> Issue Type: Bug
> Reporter: Keith Godwin Chapman
> Assignee: Nandana Mihindukulasooriya
>
> I'm implementing security scenarios in the WSO2 Mashup Server (This will allow users to access secure services using JavaScript).
> I set the password call back on the client as follows,
> axisService.addParameter(WSHandlerConstants.PW_CALLBACK_REF, new PasswordCallbackHandler(authorName));
> But unfortunatly rampart does not copy this over when making the request to obtain the token.
> Caused by: org.apache.rampart.RampartException: Password CallbackHandler not specified in rampart configuration policy or the CallbackHandler instance not available in the MessageContext
> at org.apache.rampart.builder.BindingBuilder.getSignatureBuider(BindingBuilder.java:266)
> at org.apache.rampart.builder.AsymmetricBindingBuilder.doSignature(AsymmetricBindingBuilder.java:626)
> at org.apache.rampart.builder.AsymmetricBindingBuilder.doSignBeforeEncrypt(AsymmetricBindingBuilder.java:413)
> at org.apache.rampart.builder.AsymmetricBindingBuilder.build(AsymmetricBindingBuilder.java:93)
> at org.apache.rampart.MessageBuilder.build(MessageBuilder.java:147)
> at org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:64)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.