I am unable to resolve this error of "Unable to find valid certificate path". I am setting all required system property e.g
System.setproperty(javax.net.ssl.trustStoreType,"jks")
System.setproperty(javax.net.ssl.trustStore,keystorePath)
System.setproperty(javax.net.ssl.trustStorePassword,password)
I tried setting the VM arguments, but nothing is working for me. I am using Guidewire studio localServer (jetty).
Jetty does not use JVM javax.net.ssl.* system properties to configure the SSL for specific connectors.
Look for anything in Guidewire studio that configures an SslContextFactory (the Jetty specific term for the SSL/TLS configuration belonging to a connector), and configure that.
The keystore would be taken from the JVM, so it kind of depends how you run your GW xCenter.
Since you ask about local Jetty the parameters you are looking for are
-Djavax.net.ssl.keyStore=C:\{pathToKeystoreOnYourMachine}\keystore.jks
-Djavax.net.ssl.keyStorePassword={thePasswordToBeUsed}
In order to add those on gwb runServer level you would have to add a pass through prefix gw.passthrough. resulting in for example
gwb runServer -Dgw.passthrough.javax.net.ssl.keyStore=/Java/jdk1.8.0_74/jre/lib/security/cacerts
Related
I'm trying to install Qlik Sense Desktop on Windows Server 2012 R2. The problem I believe is with the name entered as hostname during installation.
I tried using the hostname during installation process as the name of the server machine as well as the the ip address of the windows server but I get below error message whenever I try loading the Qlik sense hub app after installation
This site can’t be reached
If you're logged into the server, try https://localhost/qmc rather than the hostname. That should always work unless the services have failed to start up or something.
If you can get in there, then you can amend the accepted hostnames in the Virtual Proxy settings in the "Host Allow List" section.
If you can't get in there, it's possible it's trying to use the hostname you entered to connect between services - your best bet is to do a full uninstall and re-install - and probably keep the default hostname it proposes as this should always work and you can add additional hostnames at a later date.
Are the services up and running ? Have you see if one of the ports used by QlikSense are available or were used by other application ?
I am setting up the native windows Postman and trying to run the "Request Header" api provided in Postman Echo collection. I get the following error.
"Error: tunneling socket could not be established, statusCode=407"
I can see in the postman console that it is picking up the correct proxy server from environment. My proxy server requires authentication, how do I provide credential information. I tried to start Postman using the following command but it did not help.
postman.exe --proxy-server=userName:password#myproxy:8090
Unfortunately the proxy tab in Settings does not allow authenticated proxies.
Entering proxy info in the format "userName:password#myproxy" will cause everything before the '#' symbol to be removed.
You may already know, but since version 5.2, Postman includes a "Proxy" tab into the "Settings" section.
You should be able to configure your proxy on your system (if you are using Windows you can do it in Internet Options>>Connections>>LAN Settings) and then enable the "Use system proxy" in this tab.
After testing this method is helpful：
Windows- create a postman.bat file with the following content:
set HTTP_PROXY=http://USER:PASS#host:port
set HTTPS_PROXY=https://USER:PASS#host:port
start C:\path\to\Postman.exe
as I get this from here
In the "Global Proxy Configuration" section of the Proxy tab, setting the "Proxy Server" value to -
userName:password#proxyHost:proxyPort resolves the issue.
I could solve this problem for Postman and also for other local tools that are not capable of NTLM authentication against a proxy.
The solution is the open source proxy service/demon CNTLM that runs under Linux, macOS and Windows. The project has not been updated for a while but I could easily install and run it under Windows 10.
Best part is that it is able to check your proxy's capabilities and automatically find the latest NTLM version that the proxy supports.
http://cntlm.sourceforge.net/
You can add Proxy-Authorization header with value Basic base64encode($user:$password)
launch postman through :
vagrant#localhost:~/Downloads/Postman-linux-x64-7.6.0/Postman/app$ ./Postman
and set/unset proxy values
I'm working on a Python project that depends on a package that runs Gunicorn as a web server. I need to support https, but the Gunicorn configuration exposed by the package doesn't allow me to pass in keyfile or certfile options, and 'http' is hard-coded throughout the package.
I was wondering if there's some easy way to get https working transparently between clients and Gunicorn without Gunicorn knowing about it, on OpenShift or any popular PaaS.
Take a look at the solution purposed this Openshift KB https://www.openshift.com/kb/kb-e1044-how-to-redirect-traffic-to-https
OpenShift Online apparently handles this automatically by default.
Just change the http to https in the application url they give you (https://xxx-yyy.rhcloud.com) and you've got TLS using their *.rhcloud.com certificate.
I was expecting more configuration and just needed somebody to tell me "just change the url to https".
I am testing wso2stratos-is-1.5.2 in a stand alone mode. I unzip the product. I enter the bin directory and run ./wso2server.sh , i login as admin, I try to logout and I get the following error message in the log file
Stratos Identity]ERROR
{org.wso2.carbon.identity.sso.saml.processors.LogoutRequestProcessor}
- No Established Sessions corresponding to Session Indexes provided. {org.wso2.carbon.identity.sso.saml.processors.LogoutRequestProcessor}
I wonder if some one of greater knowledge could inform me why this happens out of the box?
What i ended up doing to fix this problem is like I said in my comment.
I copied the repository/conf/advanced directory from the working full stratos install IS Server and pasted it into the stand-alone version of Stratos IS. And made sure the port number in authenticators.xml was pointing to the stand-alone port number.
Then I copied the following files from the working Stratos IS Server and pasted into the Stand-alone version, modifying the port numbers to be relevant to the stand-alone
1. sso-idp-config.xml
2. Identity.xml
3. Carbon.xml
Now I can logout properly.
Please check whether the ACS URL in the relying party entry related to Stratos IS in the sso-idp-config.xml has the same hostname as in the hostname parameter in carbon.xml.
Thanks,
Thilina
I am having a look around bottom-up Webservice in Eclipse. Here is my environment:
Eclipse Helios
Java 1.6.0_29
Apache Axis2
Tomcat 6.x
I create Dynamic Web project and create a simple service class. And then I tried to create Webservice for the class, I got some errors like below:
IWAB0489E Error when deploying Web service to Axis runtime
axis-admin failed with {http://schemas.xmlsoap.org/soap/envelope/}Client The service cannot be found for the endpoint reference (EPR) http://localhost:8080/myws/services/AdminService
Searching web, I could not any clear answer yet. Please help me.
Thanks in advance.
I have the same problem i go Window -> Preferences -> WebServices -> Server and Runtime and set it as you see here:
Previously it was selected Tomcat 6 (i use 7) and axis1 not 2
Try these 3 methods
1) try deleting the .snap file found in
yourprojectworkspace\ .metadata\ .plugins\ org.eclipse.core.resources
2) The most common hiccup is when another web server (or any process for that matter) has laid claim to port 8080. This is the default HTTP port that Tomcat attempts to bind to at start-up. To change this, open the file:
$CATALINA_HOME/conf/server.xml
And search for '8080'. Change it to a port that isn't in use, and is greater than 1024, as ports less than or equal to 1024 require superuser access to bind under UNIX. (Example 8181)
Restart Tomcat and you're in business. Be sure that you replace the "8080" in the URL you're using to access Tomcat. For example, if you change the port to 8181, you would request the URL http://localhost:8181/ in your browser.
3) Open the bin folder which contains the shutdown.bat file residing inside the tomcat directory. Run it, that should solve the port problem.