Said API /api/authentication/validate when called with Sonar Cloud to validate the token -
- With no Authorization header - returning
{ "valid": true }-
- With Authorization header with correct bearer token - returning
{ "valid": true }-
- With Authorization header with incorrect bearer token - returning
{ "valid": false }-
When called with Sonarqube Enterprise Edition Version 10.2.1 where SAML is enabled -
- With any Authorization header - returning
{ "valid": false }-
Is there any limitation/issues/additional steps for expected results? Didn’t find anything specific in documentation.