I am trying to connect to a remote sonarqube 6.2 server from Sonarlint 3.2 plugin in eclipse neon. I am able to connect to my local server http://localhost:9000.
But When I am trying to hit the remote sonar server I am getting below error:
Fail to request https://xxxxxxxxxxxxxx:xxxx/xxx/api/system/status
Please advise.
I ran into this problem myself using SonarLint 3.1 and SonarQube 6.7.
In IntelliJ I kept running into this error message
Failed to connect to the server. Please check the configuration.
Error: Fail to request https://<SONARQUBE>/api/system/status
However I could access that URL through my browser without any issues.
When you WireShark the requests coming from the browser and the IDE you can see that the cypher suite is quite different and that the IDE plugin gets a TLS handshake failure.
That lead me to discover that Java still ships with limited strength cryptographic functions. That’s either because of US export policy or because nobody has gotten around to fixing it. The internet isn’t quite sure.
Either way, you can download the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files from Oracle: http://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html
Once I installed those onto the IntelliJ JVM, I no longer got the underlying TLS handshake failure when trying to connect to SonarQube and the connection works.
Related
I have a spring boot based microservice in which I am using Microsoft Azure Computer Vision API to read data from a PDF file. After containerizing the microservice, the container works fine and I am able to send/receive data to/from Computer Vision API on my machine. But, when I run this container on an Azure based Linux Virtual Machine, the container cannot communicate with the Computer Vision API and throws exception java.lang.RuntimeException: javax.net.ssl.SSLKeyException: RSA premaster secret error. Also, the spring-boot jar is able to communicate with Azure on VM and throws no such exception.
Do you think I need to pass any self-signed certificate to the container for it to be able to communicate smoothly?
I think the biggest advantage of using these containers is that it makes the code platform independent. So, why is this error thrown only on Azure VM and runs completely fine on my machine? Please advise.
java.lang.RuntimeException: javax.net.ssl.SSLKeyException: RSA premaster secret error
On local computer was working fine but when run the container on Azure Linux VM it is not working so there might be compatibility issue between Linux VM and Java JRE’s.
Based on above error the solution is Just remove the updated java version from your server Classpath and try to install the old java version
Please refer this link had the same discussion over here related to above error : https://community.oracle.com/tech/developers/discussion/1533888/another-rsa-premaster-secret-error
Second, try to set the SSL/TLS parameters in the java panel because An SSL certificate is a bit of code on your web server that provides security for online communications. When a web browser contacts your secured website, the SSL certificate enables an encrypted connection. It's kind of like sealing a letter in an envelope before sending it through the mail.
Supported SSL/TLS versions by JDK version
I was able to find out what the error was. There was nothing wrong with the JDK/JRE setup. The issue arose due to the version of docker engine installed on the Azure VM.
Azure based computer vision APIs required server to be TLS1.2 compliant, whereas the version of the docker engine installed on my machine was older and did not support TLS1.2. I was able to fix it after upgrading the docker engine to the latest version.
My set up is the following SonarQube 6.0 + Nginx (two docker containers) hosted on a machine on azure.
I've configured the sonar-auth-aad and it's working like a charm in the browser.
I've added the self signed certificate to the store of the local machine so I don't get an error anymore.
My machine has Vs2015 update 3 and the latest version as of today for sonarlint.
When I try to connect to the server using my AAD logins, doesn't work, although it works with plain sonarqube credentials.
Is it something not supported yet or can I configure something in order to make it work?
Thanks!
We're providing the ability from SonarLint to connect to a SonarQube server with a standard login/password just for backward compatibility reasons with SonarQube 4.5. But the official way to establish this connection is by :
Generating a user authentication token in SonarQube (See http://docs.sonarqube.org/display/SONAR/User+Token)
Configure SonarLint to use this token (and not a login/password)
From there you'll manage to have SonarLint for Visual Studio establishing a connection with your SonarQube server.
I am using WebSphere Developer Tools for Eclipse on Mars SR1. I am trying to republish my application on a remote WebSphere 8.5 server. I am running into a SSLHandshakeException error when I try to do an incremental publish.
A "Problem Occurred" dialog pops up with the following details:
The publish encountered some problems and the application may not have
been installed or it may have been successfully installed but was
unable to start. Removal of the following application is completed:
WebAppEAR Removal of the following application is completed:
WebAppEAR Failure uploading archive to server: Upload retry limit
exceeded for file
C:\Users\Administrator\workspace.metadata.plugins\com.ibm.etools.wrd.websphere.core\tmp1455916474993\TestEAR.ear.
Exception: javax.net.ssl.SSLHandshakeException: com.ibm.jsse2.util.h:
PKIX path building failed:
java.security.cert.CertPathBuilderException: PKIXCertPathBuilderImpl
could not build a valid CertPath.;
The only way I can republish my application is to remove it from the server and re-add it.
This is currently a known problem with using WebSphere Application Server on Eclipse Mars with WebSphere Developer Tools. The technote below explains what's causing this problem and a few ways work around it.
IBM Technote: http://www-01.ibm.com/support/docview.wss?uid=swg21976357
Essentially, in Mars SR1 an EPP logging plugin was added, which conflicts with WebSphere Developer Tools. This affects the republishing on WAS V7, V8 and V85 using a secure profile with non-loose configuration (Run server with resources on Server). This includes remote servers, which always run with non-loose configuration and local servers that have that option enabled.
If you choose to disable the EPP logging plugin, please refer to the link below for the latest updates. Also, for those who are using Mars v2 now, please be aware the VM argument has changed slightly after Aeri v2 was introduced.
https://wiki.eclipse.org/EPP/Logging
Also, if you are using an existing workspace and the plugin wasn't disabled, you will have to delete the plugin directory manually. The folder is called "org.eclipse.epp.logging.aeri.ide.server" and it is located here: "workspace/.metadata/.plugins/".
It happens to me whenever I use add or remove projects option to remove the projects and add it back again. When we remove the project from server using eclipse sometimes it won't get remove from actual server. So when we add back again we get this exception. So make sure the project is uninstalled from server admin console when you remove it from server. If it is not, then uninstall forcefully from admin console.
I am new to tridion and trying to setup a new instance of tridion 2011. I was able to successfully publish all my requests to file system and broker db. Suddenly it stopped publishing and all requests are stuck in "Ready to transport" mode.
I have already gone through many related threads on this forum, but could not sort out the problem. I am using Widows server 2008, with Jre 1.6 (32 bit and 64 bit both installed). Any pointer to finding the issue will be appreciated.
First thing to check is if your transport service is running.
Second thing I would look at is the config files to make sure the transport service is looking in the same directory that the publisher is storing them. Then see if files are being dropped in the transactions folder on the CM machine.
In our environment this issue arose due to a change in the SSL ciphers supported on our Content Deployer server. We are using the SSHFTP transport protocol and for security reasons the RC-4 cipher suite that had been supported by the CD server was no longer supported. We logged a case with SDL support and they issued Hotfix CD_2011.1.2.2350 which adds support for the stronger ciphers.
Unfortunately, the logs gave absolutely no indication of the issue, even with TRACE level logging.
So if you face this issue and you're using SSHFTP and the other solutions don't work for you, maybe this will help.
I have created a plugin for connecting to sql thru jdbc driver in my development server. I tried to install the plugin thru update site , but i doesnt work for me for some reason.then copied the plugin into the "domino\workspace\applications\eclipse\plugins" folder in my server. and the connection is successfull. Then i copied the same plugin in my production server, but the connection fails, it throws error saying "it could not find the driver". what could be the reason?
Extension library version is different in Development and production server. Later i upgraded my production server with latest version of extension library and the problem is solved.