skymilong opened a new issue, #32947: URL: https://github.com/apache/doris/issues/32947
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/doris/issues?q=is%3Aissue) and found no similar issues. ### Version Last code from the master branch (as of 2024-3-28 11:53:44) ### What's Wrong? There is an inconsistency between the comments and the code logic in the `getBackends` method. The comments mention that this interface will not verify user permissions, but in the code, I see a line `executeCheckPassword(request, response);`, which seems to perform permission verification. Looking further into the `executeCheckPassword` method, it calls `getAuthorizationInfo`, and `getAuthorizationInfo` returns false when the "Authorization" header information is empty. This results in the `executeCheckPassword` method throwing an `UnauthorizedException` exception.This results in the `executeCheckPassword` method throwing an `UnauthorizedException` exception. This issue has impacted the access of other connectors, in my case, I'm using flink-cdc 3.0.1. ### What You Expected? I expect the behavior of the code to be consistent with the comments. If the comments indicate that there will be no permission verification, then there should be no operation for permission verification in the code. ### How to Reproduce? here https://github.com/apache/doris/blob/2a82bb7e0d52f4901f45bf646a904bf8a3c2dad8/fe/fe-core/src/main/java/org/apache/doris/httpv2/rest/BackendsAction.java#L74 ### Anything Else? _No response_ ### Are you willing to submit PR? - [X] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
