StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
10236927
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-04-19T21:18:30.097
FavoriteCount
0
LastActivityDate
2012-04-19T21:18:30.097
LastEditDate
LastEditorUserId
0
OwnerUserId
1292294
ParentId
10070704
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
After doing some research, I found some potential solutions and like to share with you. Problem 1: Unable to apply security policies at granular level. Solution : I was able to apply security policies at 1.) root level 2.) operation level and 3.) message level using operationName & operationNamespace <pre><code><proxy name="StockQuoteProxy" transports="https http" startOnLoad="true" trace="disable"> <target endpoint="SimpleStockQuoteService_noSuspendOnFailure_TCPMon"> <inSequence> <header xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" name="wsse:Security" action="remove"/> </inSequence> <outSequence> <send/> </outSequence> </target> <publishWSDL uri="file:repository/samples/resources/proxy/sample_proxy_3.wsdl"/>  <policy key="sec_SigOnly"/>  <policy key="SigEncrSTS" operationName="getFullQuote" operationNamespace="http://services.samples"/>  <policy key="sec_InOut-Policy" operationName="getQuote" operationNamespace="http://services.samples" type="in"/> <enableSec/> </proxy> </code></pre> Problem 2: when a proxy service is deployed, published WSDL is automatically generated and we have limited/no control to customize it. Solution : Using Property useOriginalwsdl, I was able to publish original supplied WSDL with only IP/Port changed to Proxy IP/Port. <pre><code><proxy name="STSProxy" transports="https http" startOnLoad="true" trace="disable"> <target endpoint="PingSTS_UT"> <inSequence> <property name="preserveProcessedHeaders" value="true" scope="default"/> <log level="full"/> </inSequence> <outSequence> <send/> </outSequence> </target> <publishWSDL key="wsdl_sts"/> <parameter name="useOriginalwsdl">true</parameter> </code></pre> I wish WSO2 support to apply both of those solutions at the same time. i.e., able to control how published WSDL is generated and apply security policies at granular level. PS: When Security Polices are applied by directly editing in Source View, the UI is still showing Unsecured . it will only show Secured when built-in security policies are applied through Web UI or the policy name match to one of the built-in policy 
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWSO2 ESB applying security policies at binding hierarchy
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USSumanth Chinthagunta
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.