Hi,
Sorry for the late reply.
If you are implementing your own policies then you have to do two things.
a. write the custom assertion builders that would build assertions and
add them to the policy model.
b. write a piece of code that would enforce those policies (for instance
Rampart module is the piece of code that is enforcing security assertions)
So if you are your own custom assertions that would enforce security at
SOAP attachment level my guess is you have to write your own custom
assertion builders plus a module that would interpret and enforce it at
runtime.
Best,
--Sanka
Jayavarshini Radhakrishnan wrote:
Hi,
We have implemented Axis2 for trading SOAP messages. As described by Axis2,
we are using the Rampart module and Neethi policy to implement SOAP
security. However, Rampart doesn't support SwA(SOAP with Attachment)
security. Hence, I am trying to create a custom policy, which I can add it
as policy component to Neethi. However, I am unable to get any guidelines
for creating policy for securing attachments. I am new to this, so If I am
on the wrong track, please let me know. Any help/guidelines would be
appreciated.
Thanks,
Jaya
------------------------------------------------------------------------
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.503 / Virus Database: 269.17.1/1183 - Release Date: 12/13/2007 9:15 AM
--
Sanka Samaranayake
WSO2 Inc.
http://www.bloglines.com/blog/sanka
http://www.wso2.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
