You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fx-dev@ws.apache.org by "Matt Lovett (JIRA)" <ji...@apache.org> on 2006/11/02 11:10:18 UTC

[jira] Updated: (SANDESHA2-38) Extend SecurityManager to add 'apply' method

     [ http://issues.apache.org/jira/browse/SANDESHA2-38?page=all ]

Matt Lovett updated SANDESHA2-38:
---------------------------------

    Attachment: apply.patch

Here's the patch that I described when I opened the Jira.

> Extend SecurityManager to add 'apply' method
> --------------------------------------------
>
>                 Key: SANDESHA2-38
>                 URL: http://issues.apache.org/jira/browse/SANDESHA2-38
>             Project: Apache Sandesha2
>          Issue Type: Improvement
>            Reporter: Matt Lovett
>         Attachments: apply.patch
>
>
> We have an implementation of the SecurityManager that needs to put some token-related properties
> onto the message context for each RM message. The obvious way to achieve this is to add a new
> method like:
> public void apply(SecurityToken token, MessageContext outboundMessage)
> to the SecurityManager interface.
> I'll attach a patch that does this, as well as fix up the various SecurityManager impls. I'll also take the
> chance to beef up the UnitTestSecurityManager so that it uses 'apply' to add a header into the message,
> which allows us to implement a better 'checkProofOfPossession' method.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org