nope, not in sonarqube
Did you get all endpoints at once with the API ? Is yes, you need to then get the id, and get it âsoloâ by just adding the id after a slash in the endpoints
/endpoints/{id]?api-version=xxx
here you go
{
âdataâ: {},
âidâ: âxxxxxxxxxxxxxxxxxxxxxâ,
ânameâ: âSonarQubeâ,
âtypeâ: âsonarqubeâ,
âurlâ: âhttp://10.10.0.40:9000â,
âcreatedByâ: {
âdisplayNameâ: âAtif Farrukhâ,
âurlâ: âxxxxxxxxxxxxxxxxxxxxxxxxxxxâ,
â_linksâ: {
âavatarâ: {
âhrefâ: âxxxxxxxxxxxxxxxxxxxxxâ
}
},
âidâ: âxxxxxxxâ,
âuniqueNameâ: âxxxxxxxxxxxxxâ,
âimageUrlâ: âxxxxxxxxxxxxxxxxxâ,
âdescriptorâ: âwin.Uy0xLTUtMjEtNDEzNTA2ODk3Ny01ODc5MjQ0MDEtMjE4ODk1NjAyMS0xNjQ0â
},
âauthorizationâ: {
âparametersâ: {
âusernameâ: null,
âpasswordâ: null
},
âschemeâ: âUsernamePasswordâ
},
âisSharedâ: false,
âisReadyâ: true,
âownerâ: âLibraryâ
}
any update regarding this issue?
@mickaelcaro any update regarding this issue?
For reference, I have encountered this after upgrade to 8.7.1 and taken the same steps as above, creating a new Service Connection. Still finding that I get this issue, but only when using a Linux based build agent (not sure if that is relevant).
Also, looking at the logs on Sonarqube I can see it is getting a 401 when trying to reach the is_valid_license API endpoint:
[08/Apr/2021:16:30:59 +0100] âGET /api/server/version HTTP/1.0â 200 - â-â â-â âAXirv6CFEDFxZdlpAAWDâ
[08/Apr/2021:16:30:59 +0100] âGET /api/editions/is_valid_license HTTP/1.0â 401 - â-â â-â âAXirv6CFEDFxZdlpAAWEâ