unable to connect to Sonarqube via intellij (SonarLint) - intellij-idea

I am trying to integrate sonarqube(version 5.1.2) with intellij(2016.2). I have added sonarLint plugin.
when I am trying to add a sonar server to the sonarLint settings it asks for username and password for sonar server and other details like url.
But it somehow is unable to connect to the sonar server and gives error :
Fail to request : https://example.com/api/system/status

The latest version of SonarLint only supports SonarQube 5.6+ (5.6 is the current LTS version).
Apart of that, you might also be facing a problem with server SSL certificates. SonarLint will try to validate the server's SSL certificate using the JVM's truststore. So if your SonarQube server uses an SSL certificate, you might need to install the CA certificate in the trustore of the JVM used by IntelliJ.
Due to a limitation in SonarLint, certificates configured within IntelliJ aren't supported by SonarLint: https://jira.sonarsource.com/browse/SLI-75

I ran into something similar 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.

I just had the same error. After many tries, it turned out that I had to enter my login (it's a domain account) in the upper-case. Looks like login is case-sensitive.
It's my work account and I was using it always in lower-case, so it's quite surprising, but worked nonetheless.

Sorry for late response, but you can try to follow this instruction.
You can find it here. Download the Zip and follow the instructions in the pop-up after you click download.
Versions: SonarLint - IntelliJ IDEs Plugin | Marketplace (jetbrains.com)

Related

Remote development (from PhpStorm with JetBrains Gateway) without internet possible?

Here is my working context;
no internet (I use my company's intranet)
Linux CentOS 7.9 remote server with my source files
PhpStorm 2021.3.2 on my development PC
My wish is to develop on my PC on remote sources. Your new JetBrains Gateway solution seems to meet my expectations on paper.
However, in practice, I have the impression that it is not possible to use this solution without internet ? Indeed, the connection process stops on this failure:
Looks like your solution is trying to download an IDE client to install on my machine. Which from my point of view is a weird behavior because I already have a client to install on my machine: PhpStorm. Why not use my PhpStorm client already installed on my machine ?
Thank you for your reply
The "Jetbrains Client" mentioned in the error message is not for your local machine, but for the Linux server:
Once the IDE version and project directory are selected, Gateway will download the IDE to the remote server, unpack it, and launch it with your project loaded.
It acts on the remote server as a "backend IDE" to which the client on your local machine connects:
The JetBrains Client runs locally and provides the user interface for the IDE backend.
You would not even require the full PHPStorm IDE, the Jetbrains Gateway is a standalone app that comes with a "thin client" that can connect to the backend IDE:
This whole process is managed by JetBrains Gateway, a new, compact, standalone app that provides everything you need to get started with remote development. Since it’s standalone, it’s the only thing you need to install locally to start working and is ideal for less powerful laptops and in cases where a full IDE install isn’t desired.
See https://blog.jetbrains.com/blog/2021/12/03/dive-into-jetbrains-gateway/ for a more detailed look at how it works.
To answer your question: it is not possible to use Jetbrains Gateway without an internet connection.

Marklogic WebDav server connection not working after macOS Mojave upgrade

All Mac computers at my job were upgraded to macOS Mojave four days ago. Since then, no Mac users have been able to connect to any MarkLogic WebDav servers. PC users are able to connect no problem and so are Macs that are still running older versions of macOS.
Also, now when trying to connect to the WebDav server through Finder, we get this pop-up message:
"Do you want to send your name and password in a way that is insecure?
The baseURL provided uses an unsecured method for network communication. To use a secure connection, you must use a server that supports SSL."
Has anyone else encountered this issue? Is there a setting in MarkLogic that we need to change?
Thank you!
It sounds like the primary change is that macOS now issues a warning when you are connecting in a way that could send your password in clear text.
MarkLogic supports WebDAV over SSL, so to remove the warning, you will need to enable SSL on your WebDAV app server.
The MarkLogic Security Guide goes into the details of Configuring SSL on App Servers.
You can also check the WebDAV Server Configuration Help for a complete list of the available options for a WebDAV app server.
It was an Apple issue. We installed the Mojave 10.14.6 supplemental update and the problem fixed itself. We're able to connect to the WebDav servers no problem. Thanks!

Hmm... we didn't recognise that application error message

I've been implementing the API sample from GitHub. In my development environment I can logon using the OAuth method, and obtain a token and perform the query request on the XERO. If I deploy, I can't get the application to work because of the errormessage 'Hmm... we didn't recognise that application.' I can logon, then select the instance to work upon and then the error message appears. For some reason i can't obtain a token:
I get a https://app.xero.com/oauth/APIAuthorise?oauth_token=
message, in my dev env. I get a token.
I found several posts regarding this message on the Xero forum. It is written that it has to do with TLS and I should upgrade to 1.2 My issue is that my connection is already tls1.2, I verified. I tried two different hosts to do an extra check but with the same result (virtual windows 2008 server and Linux)
The Question is how to solve this issue. Again my application is working well on development, but not when I deploy. The development system is running under W10 / Xampp and PHP 7.2. My production environments are a regular Linux host (not sure what) and a virtual Windows 2008 server with uniform server.
The code is very similar to the original sample as published on GitHub, so I didn't post it here.

Support for NSS in developer-mode ChromeOS?

first question.
I recently put kubuntu onto my chromebook via crouton, which was painless and awesome. However, it did necessitate putting it into developer mode. For some reason, this has removed ChromeOS's ability to authenticate SSLs for a couple of sites I use for work (but not all of them). I prodded the sysadmin, and he says the problem is the NSS library. Specifically:
It is a problem with the NSS library version on the users OS. You can
by pass the problem by starting Chrome with;
$ google-chrome-stable --ssl-version-max=tls1.1
I tried running that command (with and without the $) in Crosh, shell, and even bios command prompt. Nope (command not found, or some variation there of). This page seems to suggest that NSS isn't favoured, but the sysadmin is unable or unwilling to change the protocol to OpenSSL. So I'm left with trying to install NSS support onto my post-crouton, dev-mode chromebook. Problem is, I have no idea how to do that. Worst case scenario, I can move my work environment totally from ChromeOS into the newly installed Kubuntu instance, but I'd rather not because ChromeOS is just such a pleasure to work on, for browser based work.
Does anyone know how to get NSS protocol SSLs working on dev-mode ChromeOS?
you cannot re-run chrome from within chrome, so that command won't help.
NSS/OpenSSL aren't protocols, they're libraries that implement protocols. Chrome OS uses NSS for some certificate management, but it uses OpenSSL (actually BoringSSL) for all network communication.
putting Chrome OS into dev mode though should not change its behavior at all when it comes to network protocol negotiation. without more details, it's hard to guess at the issue.

Adobe AIR Extension for Dreamweaver fails to connect to timestamp server

I'm having issues with creating an AIR file from an Adobe AIR HTML/JavaScript project.
I've installed the Adobe AIR Extension for Dreamweaver CS5.5 and I also have the latest x86 version of the Java Development Kit installed (which should include the Java Runtime Environment). I'm using Windows 7 (x64).
After self-signing a digital certificate through the extension, I attempted to build the project into an AIR file. However, I encountered this dialog:
There was an error connecting to the timestamp server. You may not have a connection to the network, or the server itself may have a problem.
Click Retry to try again.
Click Disable to create the AIR file with timestamping temporarily disabled. If you disable timestamping, the AIR application will fail to install when the digital certificate expires.
I checked my proxy settings in both the Java control panel and Internet Explorer, but nothing should interfere with Dreamweaver's connection. I also disabled Windows Firewall and tried another network connection, both to no avail.
After some research, I found a suggestion stating that the Geotrust timestamp server may be temporarily down. Despite this, the error still persists after I've waited a day.
Can somebody help me resolve this problem? Thanks.
I found the solution.
Java SE version 7 was installed on my computer, but version 6 was the latest version supported by the Adobe AIR tools. I downgraded to version 6 and the timestamp generation went smoothly.