[jira] [Updated] (RAMPART-426) Rampart has no support for handling actor/role attribute in the Security header

["Robert Lazarski (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/RAMPART-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Lazarski updated RAMPART-426:
------------------------------------
    Fix Version/s: 1.7.1

> Rampart has no support for handling actor/role attribute in the Security header
> -------------------------------------------------------------------------------
>
>                 Key: RAMPART-426
>                 URL: https://issues.apache.org/jira/browse/RAMPART-426
>             Project: Rampart
>          Issue Type: Bug
>          Components: rampart-core
>    Affects Versions: 1.6.2
>            Reporter: Boris Dushanov
>            Priority: Major
>              Labels: Patch
>             Fix For: 1.7.1
>
>         Attachments: actor.patch
>
>
> According to the WS-Security specification:
> "The <wsse:Security> header block provides a mechanism for attaching security-related information targeted at a specific recipient in the form of a SOAP actor/role."
> <wsse:Security S11:actor="..." S11:mustUnderstand="..."/>
> Currently, Rampart is far from full support for actor/role.
>  - RampartEngine has a bare support, taking the 'actor' attribute from a random Security header.In addition, in SOAP 1.2, the 'actor' attribute is renamed to 'role', which is not handled by the RampartEngine.
>  - Rampart message builders has no support for actor/role. 
>  - Rampart configuration has no support for actor/role also
> WSS4J has support for actor/role and such could easily be added in Rampart.Proper configuration should be added and actor/role values should be propagated to WSS4J.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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