When starting WSO2 DAS server (3.0.1), there are connection exceptions throwing out as below,
The DAS server is behind the organization proxy server and I just wonder if I can change some configurations to adapt the proxy server.
Cheers,
Sean
Usually this error is thrown as shindig is trying to load some google analytics apis. But I think this issue was fixed as I couldn't reproduce the same. Can you try the latest DAS version which will be released soon and which is available here.
Related
Vulnerable JS Library jquery-3.4.1.js reported in Wso2 identity server 5.11.0.
I recently installed wso2 identity server 5.11.0 on my linux server and intregrated my application with it.
During ZAP scan below vulnerbaility is reported:
Vulnerable JS Library jquery-3.4.1.js reported in Wso2 identity server 5.11.0
Reported URL :
https://myapplicationurl.com/authenticationendpoint/libs/jquery_3.4.1/jquery-3.4.1.js
Does WSO2 provide any fix for this. It seems the authenticationendpoint application of wso2 uses this js and I am not sure of the impact if I just replace it with higher version of jquery.
Please refer to the WSO2 Security reporting process
at https://wso2.com/security. WSO2 discourages discussing security issues in public forums.
Nevertheless, most of the reported vulnerabilities of JQuery are not a threat to WSO2IS when it comes to their usage. Because those vulnerabilities reside in specific functions of JQuery and those functions are not used at all or not used in a vulnerable way.
I am verifying the Websocket support in WSO2 API manager for one of my requirement. By default, WSO2 API Manager provides the options for configuring "WS" protocol and able to access it. But I couldn't find any configuration for "WSS" protocol support.
Is there any limitation in WSO2 API manager or is there any documentation available?
Thanks,
Sow
WebSocket support is available by default in WSO2 API Manager. Related transport configurations should be available inside the axis2.xml configuration file. You can find related documentation in the WSO2 API Manager documentation.
https://docs.wso2.com/display/AM260/Create+a+WebSocket+API
When using wss endpoint, we were able to observe some errors and we were able to get rid of the errors with the following approach.
Please include the following parameter in the SecureWebSocketInboundEndpoint.xml file which resides in the <APIM_HOME>/repository/deployment/server/synapse-configs/default/inbound-endpoints directory.
TLSv1.1,TLSv1.2
Also, please remove the following parameters from the same SecureWebSocketInboundEndpoint.xml file if the following parameters(wss.ssl.trust.store.file and wss.ssl.trust.store.pass) exist in the file.
repository/resources/security/client-truststore.jks
wso2carbon
Please use the following sample web socket client to try out and run the WSS client. Please change the variable carbonKeyStoreLocation to point to <API-M_HOME>/repository/resources/security/wso2carbon.jks. Note that port for the WSS API is 8099.
You can download the WSS client in the following WSO2 official documentation under the WSS Support section. (In the second step.)[1] Further please change the access token, web socket endpoint and the carbonKeyStoreLocation with your one to try out the scenario.
[1] https://docs.wso2.com/display/AM260/Create+a+WebSocket+API
I am very new to WSO2 and I am working through the WSO2 example Cloud to RDBMS using WSO2 Enterprise Service Bus. I have followed the example as closely as I can. When I click "TryIt" for the service I am running into an "Error connecting to the Tryit ajax proxy" I do have the axis2 server started with the command /opt/wso2esb-4.8.1/samples/axis2Server$ ./axis2server.sh and the axis2 server looks to be operating correctly. Please let me know if the example is dated or if there is something else I need to do. It is certainly missing steps that I have had to infer and I may have not known to take a step that it didn't explicitly tell me to take.
Thank you for your help.
Regards,
-Joe
Fixed by deleting artifacts from server and re-deploying (no other changes).
Has anybody managed to get XMPP protocol working successfully with WSO2ESB (WSO2 Enterprise Service Bus)?
I have managed to get the server setup correctly and it registered on Openfire as a session. From there nothing seems to work. I have deployed a service which has xmpp as a transport. The service deploys successfully but it doesn't seem to create a session on Openfire and the xmpp endpoint url appears not well formed:
xmpp://wso2esb#null/services/XMPPPOC
As you can see the domain is coming out as null.
I can find no issues in the wso2esb log or the openfire logs to indicate any problem.
Has anybody has any success using XMPP as a protocol with WSO2 products (at all, let alone ESB). It seems to be that it doesn't work and it certainly appears scantly documented.
Any suggestions would be appreciated.
I'm using visual studio 2008 to create custom reports. But I've always getting the same mistake...
The remote certificate is invalid according to the validation
procedure.
---------------------------- The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.
---------------------------- Metadata contains a reference that cannot be resolved:
'https://srv-crm/myCompany/XRMServices/2011/Organization.svc?wsdl'.
My site has multiple IIS bindings so I've tried the following. But still nothing and I got a 404 error instead.
CRM2011 is configured on two separate servers (separate sql server + client side) and I'm tring to access to the service from a test server.
What else could I check?
Any help would be welcome !
For those having troubles like these accessing the soap web services and using a https protocol, we managed to solve the issue by configuring the RTM CRM 2011 deployment with Claims based authentication and IFD access thanks to this tutorial.
Hope it will help some of you !