On Wed, Jul 6, 2011 at 9:10 PM, Prabath Siriwardena <[email protected]>wrote:
> The restriction is only for the UsernameToken security scenario only.. > You can use the UI wizard with your custom policy to make UT work over > HTTP or JMS - where the user takes the responsibility of making the > underlying transport secure. > Ok, I think we can resolve the issue [0] saying invalid?. If a user wants to publish a service over CSG and also that service is secured using UT, user need to write his own policy, he/she should not use default one that comes with UI. Rajika [0] - https://wso2.org/jira/browse/STRATOS-1264 > > Thanks & regards, > -Prabath > > On Wed, Jul 6, 2011 at 8:40 PM, Rajika Kumarasiri <[email protected]> wrote: > > This is a problem for CSG agent. When UT is enabled for a back end > service > > and when we try to publish (and enable JMS for that service in the > process) > > this issue occurs. > > Why do we have this restriction in the UI ? > > Rajika > > > > On Wed, Jul 6, 2011 at 5:52 PM, Prabath Siriwardena <[email protected]> > > wrote: > >> > >> IIRC this restriction only applies if you apply UT via wizard. But if > >> you want to use JMS over TLS and use UT - you can create your custom > >> security policy with UT and apply it via wizard. > >> > >> Thanks & regards, > >> -Prabath > >> > >> On Wed, Jul 6, 2011 at 5:00 PM, Rajika Kumarasiri <[email protected]> > wrote: > >> > When I tried to expose a UT enabled service on JMS I am ending up with > >> > the > >> > following error. > >> > ERROR {org.wso2.carbon.cloud.csg.agent.jms.JMSServicePublisher} - > Cloud > >> > not > >> > publish service 'SimpleStockQuoteService'. Cannot add non-HTTPS > >> > transport > >> > binding for Service [SimpleStockQuoteService] since a security > scenario > >> > which requires the service to contain only the HTTPS transport binding > >> > has > >> > been applied to this service. > >> > org.apache.axis2.AxisFault: Cannot add non-HTTPS transport binding for > >> > Service [SimpleStockQuoteService] since a security scenario which > >> > requires > >> > the service to contain only the HTTPS transport binding has been > applied > >> > to > >> > this service. > >> > > >> > See ServiceAdmin.java:971 (on 3.2.0 branch). There is a comment saying > >> > that > >> > it need to be added but commented for the moment. Any idea why it's > keep > >> > like that ? Are we going to fix it ? > >> > Rajika > >> > _______________________________________________ > >> > Carbon-dev mailing list > >> > [email protected] > >> > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > >> > > >> > > >> > >> > >> > >> -- > >> Thanks & Regards, > >> Prabath > >> > >> http://blog.facilelogin.com > >> http://RampartFAQ.com > >> _______________________________________________ > >> Carbon-dev mailing list > >> [email protected] > >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > > _______________________________________________ > > Carbon-dev mailing list > > [email protected] > > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > > > > -- > Thanks & Regards, > Prabath > > http://blog.facilelogin.com > http://RampartFAQ.com > _______________________________________________ > Carbon-dev mailing list > [email protected] > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
