I'm testing the sample app shared by IBM (InvokingAdapterProceduresHybridProject). The firewall recognizes the adapter call as "HTTP Parser Attack" with an error "Check maximum number of header".
I'm unable to proceed further. Please help with inputs.
Talk with your IT department to allow such calls to pass. This is not related to MobileFirst, and related to your firewall.
Related
We started to get failed messages when refreshing extracts based on Bigquery
When looking at the error in the TABLEAU Server we see the next error:
Did you encounter a similar problem?
What did you do to sort this out?
Thanks!
Daniel
Resolution from the Tableau Knowledge Base:
As a troubleshooting step, check whether you can access "https://www.googleapis.com/auth/bigquery" on the affected computer using an internet browser.
Work with your internal IT to ensure that your firewall or antivirus allows communication to "https://www.googleapis.com/auth/bigquery".
The problem was the Big Query API IP being blocked, IT took care
Im trying to access a remote wcf function in a service from the test application (Client), while executing it says service expired.
I tried
1) disabling firewall,
2) checked with SSl certificates, but didn't helped me
Could anyone help me why im unable to call this wcf function running on remote machine.
First steps: enable logging.
See
https://learn.microsoft.com/en-us/dotnet/framework/wcf/diagnostics/configuring-message-logging
And:
https://learn.microsoft.com/en-us/dotnet/framework/wcf/diagnostics/tracing/recommended-settings-for-tracing-and-message-logging
To look at the logs, use this: https://learn.microsoft.com/en-us/dotnet/framework/wcf/diagnostics/viewing-message-logs
If the logs do not make sense, post back here.
We currently use a solution with WCF web services with Windows Identity Foundation for security.
It works fine for three years now, but it seems we have certain users (I mean windows users) which cannot connect to WCF.
From the same machine with four different Users, Two can connect to the application and two cannot.
Everybody see the server part (the first call was a wsHttpBinding call to check if server exist, if failed a message is provided else we display the login window) but it failed with services with Authentication(ws2007FederationHttpBinding). It seems to be a problem from Windows User...
Has anybody already encounter this type of problem? Any idea to solve it?
We do not have physically access to the machine (client machine) and cannot make some debug to see where it comes from.
the returned exception is:
Could not start session - Exception: SOAP security negotiation with "My service complete address"
for target "My service complete address" failed.
For a variety of reasons, I need programatic JavaScript access the the hostname or IP address of the Worklight server from the client code.
For example:
- I want to pull scripts and resources from the same host as the Worklight server
- I have an out-of-band service on the Worklight host and I want to connect to it
#IdanAdar has said that the address does not exist. I've search the WL object and cannot find it either. See Can we get the app version and IP address info using worklight api?.
Note that document.location.hostname is null when running as a native app.
My current workaround is to set the IP Address / hostname as a global variable in my top-level html file. This is not ideal because it causes my sourcecode to have to vary by implementation.
Worklight already has this value externalized in the application-descriptor.xml
The server side API has this exposed in WL.Server.configuration["local.IPAddress"]. I think the client should expose an API similar to this as well.
Although not the best option you can develop an adapter that returns the WL.Server.configuration["local.IPAddress"] if available, also could be possible to acces to the IP through the http request.
Is it possible to access to the HTTPRequest in the worklight adapter implementation?
I'm not sure if you can invoke adapters before wlCommonInit, if you can not and you need the ip before the common init then this approach is useless.
I built a WCF service that exposes itself for a web application, it accepts an object and prints the data on the clients machine. Works fine on my development machine, and the service is up and running on any machine i install it on. I can enter ip address in clients machine web browser and see it is running. Problem is when i send the object to the clients machine it returns an error, that sounds like it could be because of the clients windows firewall. Where would i start at to deal with this problem ?
There was no endpoint listening at http://192.168.1.168:2202/PrintLabel that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
And the InnerException: Unable to connect to the remote server
With further research and discussion with people in the community i came to understand that as was mentioned at the bottom of this article.
"Self-hosted HTTP addressing for WCF is not integrated into the Windows firewall. An exception must be added to the firewall configuration to allow inbound connections using a particular URL.
But this SO question led me to a page with how to control Windows Firewall through code to enable my WCF self hosted service to accept an object.
This the link below.
http://www.shafqatahmed.com/2008/01/controlling-win.html
That link was towards the direction i needed, but based on user comments it seemed to have some bugs. A colleague found this link and i believe this technique will be the best solution for this scenario.