Authentication against sonarqube fails about code-quality-game

[mechero]

Hi Miriam,

I tried connecting with Sonarqube 7.5 using authentication and it worked. At the bottom of this answer are the steps I made, however, looking at the stacktrace, that doesn't seem related to Authorization but to network access. If you pass localhost as environment variable, the Quboo Docker container will try to find Sonarqube in its own container, but that's not what you want.

In case it's a Connection issue

If you installed Sonarqube in the host and Quboo is running with Docker, what you want is access from the Quboo container to the host. See https://docs.docker.com/docker-for-windows/networking/#known-limitations-use-cases-and-workarounds

Basically, it should be fine if you're using Docker 18 or above to replace localhost by host.docker.internal.

In case it's the token

1. Create a token in Sonarqube (for an account with access to users and issues)

2. Passed this token as an environment variable to Quboo (e.g. via .env file existing in the same folder as the docker-compose file). This is the step you might be doing wrong, if the environment variable has a typo or is misconfigured you might get those 401 codes.

SONAR_TOKEN=3da17bb876d3599147ad6e9d15cf26afe4318961

Let me know if any of these solutions work for you. I'll update the docs for the case you're trying to run.

[mimitecan]

Dear Moses,

thank you very much for your help! It was indeed the localhost setting in my config file that caused the issue - I replaced it with the constant that you suggested and the qube answered to the request of quboo.

quboo-backend_1 | 2019-01-14 08:19:05.646 INFO 1 --- [ main] o.s.j.e.a.AnnotationMBeanExporter : Registering beans for JMX exposure on startup
quboo-backend_1 | 2019-01-14 08:19:05.707 INFO 1 --- [ main] s.a.ScheduledAnnotationBeanPostProcessor : No TaskScheduler/ScheduledExecutorService bean found for scheduled processing
quboo-backend_1 | 2019-01-14 08:19:05.731 TRACE 1 --- [pool-1-thread-1] c.t.d.m.u.service.SonarUsersRetriever : Retrieving users, page 1
quboo-backend_1 | 2019-01-14 08:19:05.813 TRACE 1 --- [pool-1-thread-1] c.t.d.m.u.service.SonarUsersRetriever : URI: http://host.docker.internal:9000/api/users/search?p=1&ps=500
quboo-backend_1 | 2019-01-14 08:19:05.855 INFO 1 --- [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat started on port(s): 8080 (http) with context path ''
quboo-backend_1 | 2019-01-14 08:19:05.876 INFO 1 --- [ main] c.t.devgame.Application : Started Application in 14.935 seconds (JVM running for 17.015)
quboo-backend_1 | 2019-01-14 08:19:07.219 INFO 1 --- [pool-1-thread-1] c.t.d.m.u.service.SonarUsersRetriever : Adding new user: USR1@SOMECOMPANY
quboo-backend_1 | 2019-01-14 08:19:07.314 INFO 1 --- [pool-1-thread-1] c.t.d.m.u.service.SonarUsersRetriever : Adding new user: USR2@SOMECOMPANY
quboo-backend_1 | 2019-01-14 08:19:07.325 INFO 1 --- [pool-1-thread-1] c.t.d.m.u.service.SonarUsersRetriever : Adding new user: USR3@SOMECOMPANY
quboo-backend_1 | 2019-01-14 08:19:07.341 INFO 1 --- [pool-1-thread-1] c.t.d.m.u.service.SonarUsersRetriever : Adding new user: USR4@SOMECOMPANY

However, I still can't see any users in my quboo-gui despite the backend saying that it has added 227 users to the database.

Maybe you could give me another advice why this is the case?

Regards,

Miriam

[mechero]

I think what you're seeing now is due to the fact that you didn't add users to teams. Navigate to the Organizer, make sure you can see non-assigned players (by checking the checkbox), create one or more teams and assign players to them. Hope that helps.

[mimitecan]

It did indeed! Works like a charm - thank you very much.