Unable to Create new organization in sonarcloud failed with a linkedIn in error

SonarQube Cloud
1

Linking new Azure DevOps organization in SonarQube Cloud fails with an error.

  • ALM used - Azure DevOps
  • CI system used - Azure DevOps
  • Error Observed
    Access to XMLHttpRequest at ‘https://px.ads.linkedin.com/wa/’ from origin ‘https://sonarcloud.io’ has been blocked by CORS policy: The value of the ‘Access-Control-Allow-Origin’ header in the response must not be the wildcard ‘*’ when the request’s credentials mode is ‘include’. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute.
    {2946B5A7-7F5C-4CB1-A5D4-0CBC592C8E37}
    {2946B5A7-7F5C-4CB1-A5D4-0CBC592C8E37}829×819 54.2 KB

Also noticed this error in developer tools console
GET https://api.sonarcloud.io/dop-translation/dop-organizations?devOpsPlatform=azure&devOpsPlatformOrganizationId=Test123 400 (Bad Request)

I am on a cooperate laptop and we use zscaler. the urls sonarcloud.io & *.sonarcloud.io are not blocked as could see my traffic allowed in the zscaler logs.

2

Hi,

Welcome to the community!

Could we get a screenshot of this LinkedIn error?

 
Thx,
Ann

3

The linkedIn error is on the right. in dev tools and also was saw px.ads.linkedin.com being blocked in the zScaler logs as is classified as social media link.

image
image1882×872 125 KB

I asked my security team to allow the linkedIn link that is blocked in ZScaler temporarily just to test and this is what i see now. we don’t see any more blocks in zScaler but see this in developer tool.

{EAE5F543-548C-4776-BBDA-64112FE257E1}
{EAE5F543-548C-4776-BBDA-64112FE257E1}1915×812 80.4 KB

5

Hi,

Thanks for the screenshots. I’m pretty certain those LinkedIn calls aren’t from us, but I can’t imagine where they are coming from. I’ve flagged this for more expert eyes.

 
Thx,
Ann

9

Thanks Ann,
Any idea but the second error..

{2067F33A-06DA-4FFE-AFC8-ADC5A0A36949}
{2067F33A-06DA-4FFE-AFC8-ADC5A0A36949}1904×889 119 KB

10

Hi,

None. I think we should get the first set out of the way first, and see if that doesn’t let the rest resolve itself.

 
Ann

1 Like
14

any ideas on how to resolve this. thanks

17

Hello @olu ,

I am looking into this and will keep you updated.

Best,
Chrislain

1 Like
19

Hi Olu,

After investigation, we are quite confident that zscaler is the culprit. It is not blocking the call per se but it strips some parts of the header. Please check with your network security team again so that your calls are not altered.

As a reference, here is some documentation from zscaler that might help.

Best,
Chrislain

2 Likes