[
https://issues.apache.org/jira/browse/RAMPART-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553933
]
Nandana Mihindukulasooriya commented on RAMPART-126:
----------------------------------------------------
I think this will be very useful. When thinking about the implementation of
this without violating ws - security policy language specification, two
questions came to my mind.
1. How can we define this key using a token assertion
2. How can we create reference to this key
As ws - security policy language is open for extension we define a new token
assertion for this and define a standard way to reference these keys. But then
it will break the interoperability. If there is a way to get requirement done
using default security policy assertions defined in the specification we can
make this interoperable too. Can we use a SecurityContextToken for this ? and
may be a SHA1 of the binary key as the reference ?
> Support "Known Key" symmetric encryption and/or signature with WS-Policy
> ------------------------------------------------------------------------
>
> Key: RAMPART-126
> URL: https://issues.apache.org/jira/browse/RAMPART-126
> Project: Rampart
> Issue Type: Improvement
> Components: rampart-policy
> Reporter: Paul Fremantle
>
> Suppose I have two Rampart engines talking, and I want a quick and easy way
> to set up encryption between them, I would like to use symmetric key
> encryption. I simply want to put the key into the config of each engine and
> then let them talk. That way I have no need to specify keystores,
> certificates, etc. This is equivalent to sample09 in the old config style.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
