What are you trying to accomplish?
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 24.416 s
[INFO] Finished at: 2023-08-02T13:03:47+05:30
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.9.1.2184:sonar (default-cli) on project awcp-base-pom: You’re not authorized to run analysis. Ple
ase contact the project administrator. → [Help 1]
Do we need to provide any particular access or do we need to update sonar scanner maven plugin in pom.xml…?
Support a new language?
Extend an existing one? Which one?
Add language-agnostic features?
Something else?
What’s your specific coding challenge in developing your plugin?
And, if relevant, please share the code that’s giving you problems:
9.9.1 LTS. We are using LDAP authentication. And I have created one functional account and generated token and provided that token to developers.
And we trying to test our code manually from local system.
Also, I have one question here. Can’t we able to login with project token.
==============================================
[INFO] SCM Publisher 49/49 source files have been analyzed (done) | time=1779ms
[INFO] CPD Executor 18 files had no CPD blocks
[INFO] CPD Executor Calculating CPD for 20 files
[INFO] CPD Executor CPD calculation finished (done) | time=32ms
[INFO] Load New Code definition
[INFO] Load New Code definition (done) | time=140ms
[INFO] Analysis report generated in 324ms, dir size=718.7 kB
[INFO] Analysis report compressed in 2161ms, zip size=240.6 kB
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 55.864 s
[INFO] Finished at: 2023-08-04T17:25:11+05:30
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.9.1.2184:sonar (default-cli) on project PersonMsg: You’re not authorized to run analysis. Please contact the p
roject administrator. → [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
This is a free community forum. Sometimes it requires time to look through everything, while managing the rest of the Community. Please do not bump threads and familiarize yourself with the FAQ.
This is an open community with people volunteering their free time to provide assistance. We’re eager to contribute to the community, but you are not guaranteed a fast response.
While possible that SonarQube is returning the 403, it might also be coming from a layer in between your client and the SonarQube server, namely whatever is serving it over HTTPS, like a reverse proxy (think IIS, Apache, Nginx, a load balancer…)
Let’s see if the request even makes it to the SonarQube server. Do you see the 403 in the access.log of your SonarQube server?
And still, none of them are the same 403 that is being returned when the analysis is submitted by the scanner.
Try running the analysis again (today) and see if it appears in the logs. If not, then you’re right (from your deleted post), the issue is probably at the AWS load balancer.
A 401 would indicate that no authentication details are being provided at all. Are you still providing authentication information? Have you tried providing a new token?
Does this work locally still, as you mentioned before?