Thanks Chamara. But I'm aware of those steps and have already tested it with ESB 4.9.0 using Dev Studio.
My concern here is how customers are going to migrate their secured artifacts without re-creating them. On Thu, Jul 16, 2015 at 5:56 PM, Chamara Silva <[email protected]> wrote: > I've used following way to enable security to the proxy service from Dev > Studio project. I think this will help you. > > > 1. Create the policy > > 1. Create a proxy service from ESB management console. (lets say > passthroughProxy) > 2. Apply security (Username token) from management console > 3. Go to the source view of passthroughProxy and you may see something > like follows is added to that. > > <parameter name="ScenarioID">scenario1</parameter> > > <enableSec/> > > <policy > key="conf:/repository/axis2/service-groups/passthrough/services/passthrough/policies/UTOverTransport"/> > > > > 2. Browse the registry from management console to locate the > /repository/axis2/service-groups/passthrough/services/passthrough/policies/ > and > download the UTOverTransport file and rename it as UTOverTransport.xml > > > > 3. Create a registry resource from policy > > 1. Create a registry resource project from devstudio > 2. Create a registry resource and choose “import from file system” in > the wizard and point to the UTOverTransport.xml which we have > downloaded in 4. > > 4. Apply security to your proxy service. > > 1. Create a ESB project and proxy service if you don’t have already. > 2. Go to the proxy service properties as in[1] and configure > securtyEnable=true and policyKey. When setting policy key you have to point > to the registry resource we created in 2.2 > 3. Additionally add the following parameter in ServiceParameters > section. > > property name=allowRoles value= admin > > > 5. Once you configured you will see the source of your proxy config as > follows > > <proxy xmlns="http://ws.apache.org/ns/synapse"; > name="LoopBackProxy" transports="http https" startOnLoad="true" > trace="disable"> > > <target> > > <inSequence> > > <log level="full"/> > > <respond/> > > </inSequence> > > <outSequence/> > > <faultSequence/> > > </target> > > <policy key="conf:custom/UTOverTransport.xml"/> > > <parameter name="allowRoles">admin</parameter> > > <enableSec/> > > </proxy> > > 6. Deploy > > 1. Create a composite application project > 2. Tick (check) your proxy from ESB project and UTOverTransport from > Registry project to include them to the project. When adding use server > role as EnterpriseServiceBus for both proxy and policy since we are going > to deploy both in ESB > 3. Right click on created composite project and select “Export as > Deployable archive” > > > Thanks, > Chamara Silva > > On Thu, Jul 16, 2015 at 5:10 PM, Sandapa Handakumbura <[email protected]> > wrote: > >> [removing support-dev] >> >> >> On Thu, Jul 16, 2015 at 4:55 PM, Sandapa Handakumbura <[email protected]> >> wrote: >> >>> Hi ESB team, >>> >>> Since Applying QOS is moved completely to developer studio from ESB >>> 4.9.0 release (no UI support in ESB), do we have a way to migrate services >>> that has QOS applied (secured proxy services etc..)? >>> >>> We can't just copy those artifacts to ESB 4.9.0. I tried but it's not >>> supported (Issue reported at [1]). Is there some workaround or are we going >>> to fix it? >>> >>> [1] https://wso2.org/jira/browse/ESBJAVA-3909 >>> >>> Thanks, >>> Sandapa >>> >>> -- >>> Sandapa Handakumbura >>> Associate Technical Lead >>> WSO2.Inc. ; http://wso2.com/ >>> M : +94777115866 >>> >> >> >> >> -- >> Sandapa Handakumbura >> Associate Technical Lead >> WSO2.Inc. ; http://wso2.com/ >> M : +94777115866 >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Suminda Chamara Silva > Associate Technical Lead > WSO2 Inc. > Mobile: +94718302858 > blog: http://chamaras.blogspot.com > > -- Sandapa Handakumbura Associate Technical Lead WSO2.Inc. ; http://wso2.com/ M : +94777115866
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
