On Wed, Jul 6, 2011 at 9:10 PM, Prabath Siriwardena 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
On Wed, Jul 6, 2011 at 9:10 PM, Prabath Siriwardena 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
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.
Thanks & regards,
-Prabath
On Wed, Jul 6, 2011 at 8:40 PM,
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 wrote:
> IIRC this res
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 wrote:
> When I tried to expose
On Wed, Jul 6, 2011 at 5:10 PM, Rajika Kumarasiri wrote:
>
>
> On Wed, Jul 6, 2011 at 5:04 PM, Afkham Azeez wrote:
>
>> UT secured services can run only on HTTPS. The password is sent in
>> plaintext assuming that there is transport level security.
>
>
> I don't think this is the case. TLS is su
On Wed, Jul 6, 2011 at 5:04 PM, Afkham Azeez wrote:
> UT secured services can run only on HTTPS. The password is sent in
> plaintext assuming that there is transport level security.
I don't think this is the case. TLS is supported by JMS too. Only
requirement is to not to expose it in http.
Ra
On Wed, Jul 6, 2011 at 5:04 PM, Afkham Azeez wrote:
> UT secured services can run only on HTTPS. The password is sent in
> plaintext assuming that there is transport level security.
>
>
> On Wed, Jul 6, 2011 at 5:00 PM, Rajika Kumarasiri wrote:
>
>> When I tried to expose a UT enabled service on
UT secured services can run only on HTTPS. The password is sent in plaintext
assuming that there is transport level security.
On Wed, Jul 6, 2011 at 5:00 PM, Rajika Kumarasiri wrote:
> When I tried to expose a UT enabled service on JMS I am ending up with the
> following error.
>
> ERROR {org.w
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 s
10 matches
Mail list logo
