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 "Davanum Srinivas (JIRA)" <ji...@apache.org> on 2007/01/26 20:09:49 UTC
[jira] Moved: (RAMPART-16) Rampart needs to provide an ability to
generate separate security headers for different actions with distinct
actors
[ https://issues.apache.org/jira/browse/RAMPART-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davanum Srinivas moved AXIS2-1876 to RAMPART-16:
------------------------------------------------
Component/s: (was: modules)
Affects Version/s: (was: 1.1)
(was: 1.2)
(was: nightly)
Key: RAMPART-16 (was: AXIS2-1876)
Project: Rampart (was: Axis 2.0 (Axis2))
> Rampart needs to provide an ability to generate separate security headers for different actions with distinct actors
> --------------------------------------------------------------------------------------------------------------------
>
> Key: RAMPART-16
> URL: https://issues.apache.org/jira/browse/RAMPART-16
> Project: Rampart
> Issue Type: New Feature
> Reporter: George Stanchev
>
> Currently rampart generates a single wsse header with the default actor (actor attribute omitted).
> It needs to provide a way to create actions which result in different named security headers and it needs
> to provide API to set the names of those headers
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.