Hi All, I’m facing some issues trying to use NOSONAR comment on web.config XML, and it keeps marking as Security Issue, as you can see below, this is token to be replaced during the runtime and not a hardcoded secret as it sugests:
After doing some testing, I don’t think that NOSONAR is supported for XML files. I’m a bit surprised that this hasn’t come up before!
I’ve flagged this for an internal review. In the meantime, you can continue to suppress these issues either by accepting them in the UI, or excluding specific rule on specific files.
Hi @Colin, thank you for replying back. Sure, I’ve already marked this issue as False-Positive on sonar UI, but this is a good one to be fixed, I’d apreciate to have this feature soon.