Change sonar rule from Security Hotspot to Blocker issue

Clean Code New rules / language support
, , ,
1

Hi Sonar team,

I’ve been working on the rule Hard-coded credentials are security-sensitive (python:S2068) to get more sensitive words but I’ve noticed that it’s not behaving like a blocker and just as security-hotspot, and I’d like to set this rule as a blocker issue, could you please help?

3

Hi All, Any updates on this?

Regards.

5

Hi Paulo,

Unfortunately, it is currently not possible to change the severity type of our rules.

Best regards

Sebastien

8

Hi @sebastien.andrivet, thanks for replying, but there’s no possibility to set this as a blocker issue?

Regards,

9

Which version of SonarQube are you using?

10

Hi, I’m using 9.9.1.69595.

regards.

11

Hi,

I just checked with version 9.9.3 and can confirm that this is not possible.

Best regards
Sebastien

13

Hi @sebastien.andrivet,

What’s your advice on that? Any similar approach?

I do really need to set this as blocker when sonar finds a password or secret hardcoded.

Could you please suggest?

Regards.

17

Hi @sebastien.andrivet,

Any follow-up/updates regarding my last question?

Thanks

19

Hello, @sebastien.andrivet.

Any updates so far?

Regards.

20

Hi,
No sorry I do not have any news on this topic. This is not currently possible and, as far as I know, it is not planned to add such functionality.
Best regards
Sebastien

21

Ok thanks for your time!
Regards

22

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.