On Tue, Jan 11, 2011 at 8:15 AM, Amila Suriarachchi am...@wso2.com wrote:
On Mon, Jan 10, 2011 at 10:05 PM, Afkham Azeez az...@wso2.com wrote:
This requirement is different. In the case of some organizations, the WSDL
is copyrighted and distributed out of band. People who get access to
As per https://issues.apache.org/jira/browse/AXIS2-3316 I have implemented
this functionality where you can add the parameter
name=exposeServiceMetadatafalse/parameter parameter to the axis2.xml or
services.xml file in order to restrict access to the service metadata.
Adding the parameter to
+1
This is a very useful feature
Thanks regards,
-Prabath
On Mon, Jan 10, 2011 at 5:10 PM, Afkham Azeez az...@wso2.com wrote:
As per https://issues.apache.org/jira/browse/AXIS2-3316 I have implemented
this functionality where you can add the parameter
On Mon, Jan 10, 2011 at 7:44 PM, Amila Suriarachchi am...@wso2.com wrote:
hi,
First I think just restricting access to a service meta data won't make any
thing secure.
But - it makes things harder - specially in the case where a security policy
being attached..
One can argue that this
This requirement is different. In the case of some organizations, the WSDL
is copyrighted and distributed out of band. People who get access to these
WSDLs may need to sign a NDA. So, in their deployment, they would allow
authorized users to call the service, but they do not want anybody to get
On Mon, Jan 10, 2011 at 10:05 PM, Afkham Azeez az...@wso2.com wrote:
This requirement is different. In the case of some organizations, the WSDL
is copyrighted and distributed out of band. People who get access to these
WSDLs may need to sign a NDA. So, in their deployment, they would allow
On Mon, Jan 10, 2011 at 10:01 PM, Prabath Siriwardana prab...@wso2.comwrote:
On Mon, Jan 10, 2011 at 7:44 PM, Amila Suriarachchi am...@wso2.comwrote:
hi,
First I think just restricting access to a service meta data won't make
any thing secure.
But - it makes things harder - specially
On Mon, Jan 10, 2011 at 10:19 PM, Afkham Azeez az...@wso2.com wrote:
On Mon, Jan 10, 2011 at 10:01 PM, Prabath Siriwardana prab...@wso2.comwrote:
On Mon, Jan 10, 2011 at 7:44 PM, Amila Suriarachchi am...@wso2.comwrote:
hi,
First I think just restricting access to a service meta data
Also - IIRC in asmx web services by default the wsdl is accessible only from
the localhost..
Thanks regards,
-Prabath
On Mon, Jan 10, 2011 at 10:38 PM, Afkham Azeez az...@wso2.com wrote:
FYI, IIS supports something similar. e.g.
webServices
wsdlHelpGenerator href=helpPage.aspx/
protocols
On Mon, Jan 10, 2011 at 10:05 PM, Afkham Azeez az...@wso2.com wrote:
This requirement is different. In the case of some organizations, the WSDL
is copyrighted and distributed out of band. People who get access to these
WSDLs may need to sign a NDA. So, in their deployment, they would allow
10 matches
Mail list logo