Re: [Architecture] Configuring transport and security policy in dataservice config
Hi, Earlier I had the idea that ESB is also doing the same thing, and thought it is easier, where it needed lesser properties, and didn't really think the policy could be re-used by other services, but later I also got to know, that is not the case. So yeah, in that case, lets have another property like policyKey or policyPath to give the path to policy. Cheers, Anjana. On Thu, Aug 21, 2014 at 9:01 AM, Selvaratnam Uthaiyashankar shan...@wso2.com wrote: Why do you prefer convention over explicit policy location. For example, I have Data service 1, 2, 3. Data service 1 and 2 are using policy 1. Data service 3 is using policy 2. With using convention, either you can have 1 policy or 3 policy for above case. You will not be able to have only 2 policy. On Wednesday, August 20, 2014, Anjana Fernando anj...@wso2.com wrote: Hi Chanika, Lets just put enableSec as an attribute in the root element of the data service configuration. Like, data enableSec=true .. and as for the policy file location, I guess there is a standard location the ESB would look up if its not given explicitly, we will also just skip the policy location attribute and just go by convention where the policy file would be located. Cheers, Anjana. On Wed, Aug 20, 2014 at 2:17 PM, Chanika Geeganage chan...@wso2.com wrote: Hi, We recently came across a requirement to support QoS related configurations to .dbs file itself rather than adding a separate services.xml file. Therefore we are going to add the transport and security policy related configurations in the same way that in ESB proxy services configurations. The changes are: 1. Adding transports=https http attribute to configure transport info 2. Adding enableSec tag with the policy key to configure security i.e: policy key=path/to/policy/ enableSec/ In the deployment time these configurations will be extracted. Will this be a good approach to follow? Thanks -- Best Regards.. Chanika Geeganage Software Engineer WSO2, Inc.; http://wso2.com -- *Anjana Fernando* Senior Technical Lead WSO2 Inc. | http://wso2.com lean . enterprise . middleware -- S.Uthaiyashankar VP Engineering WSO2 Inc. http://wso2.com/ - lean . enterprise . middleware Phone: +94 714897591 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- *Anjana Fernando* Senior Technical Lead WSO2 Inc. | http://wso2.com lean . enterprise . middleware ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Configuring transport and security policy in dataservice config
Why do you prefer convention over explicit policy location. For example, I have Data service 1, 2, 3. Data service 1 and 2 are using policy 1. Data service 3 is using policy 2. With using convention, either you can have 1 policy or 3 policy for above case. You will not be able to have only 2 policy. On Wednesday, August 20, 2014, Anjana Fernando anj...@wso2.com wrote: Hi Chanika, Lets just put enableSec as an attribute in the root element of the data service configuration. Like, data enableSec=true .. and as for the policy file location, I guess there is a standard location the ESB would look up if its not given explicitly, we will also just skip the policy location attribute and just go by convention where the policy file would be located. Cheers, Anjana. On Wed, Aug 20, 2014 at 2:17 PM, Chanika Geeganage chan...@wso2.com javascript:_e(%7B%7D,'cvml','chan...@wso2.com'); wrote: Hi, We recently came across a requirement to support QoS related configurations to .dbs file itself rather than adding a separate services.xml file. Therefore we are going to add the transport and security policy related configurations in the same way that in ESB proxy services configurations. The changes are: 1. Adding transports=https http attribute to configure transport info 2. Adding enableSec tag with the policy key to configure security i.e: policy key=path/to/policy/ enableSec/ In the deployment time these configurations will be extracted. Will this be a good approach to follow? Thanks -- Best Regards.. Chanika Geeganage Software Engineer WSO2, Inc.; http://wso2.com -- *Anjana Fernando* Senior Technical Lead WSO2 Inc. | http://wso2.com lean . enterprise . middleware -- S.Uthaiyashankar VP Engineering WSO2 Inc. http://wso2.com/ - lean . enterprise . middleware Phone: +94 714897591 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Configuring transport and security policy in dataservice config
Hi Anjana, ESB already has a key to the policy path. I think from a platform perspective you need to follow the same. Thanks, Johann. On Wed, Aug 20, 2014 at 3:17 PM, Anjana Fernando anj...@wso2.com wrote: Hi Chanika, Lets just put enableSec as an attribute in the root element of the data service configuration. Like, data enableSec=true .. and as for the policy file location, I guess there is a standard location the ESB would look up if its not given explicitly, we will also just skip the policy location attribute and just go by convention where the policy file would be located. Cheers, Anjana. On Wed, Aug 20, 2014 at 2:17 PM, Chanika Geeganage chan...@wso2.com wrote: Hi, We recently came across a requirement to support QoS related configurations to .dbs file itself rather than adding a separate services.xml file. Therefore we are going to add the transport and security policy related configurations in the same way that in ESB proxy services configurations. The changes are: 1. Adding transports=https http attribute to configure transport info 2. Adding enableSec tag with the policy key to configure security i.e: policy key=path/to/policy/ enableSec/ In the deployment time these configurations will be extracted. Will this be a good approach to follow? Thanks -- Best Regards.. Chanika Geeganage Software Engineer WSO2, Inc.; http://wso2.com -- *Anjana Fernando* Senior Technical Lead WSO2 Inc. | http://wso2.com lean . enterprise . middleware ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- Thanks Regards, *Johann Dilantha Nallathamby* Associate Technical Lead Product Lead of WSO2 Identity Server Integration Technologies Team WSO2, Inc. lean.enterprise.middleware Mobile - *+9476950* Blog - *http://nallaa.wordpress.com http://nallaa.wordpress.com* ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
