youngkermit8-coder opened a new issue, #1664: URL: https://github.com/apache/rocketmq-dashboard/issues/1664
### Description The runtime `requireLogin` toggle and the static `studio.auth.login-required` property are both enforced by `AuthInterceptor`. However, `GET /api/auth/status` reports only the static property. When the static property is disabled and runtime settings enable login protection, protected API calls correctly require authentication, but the status response says `loginRequired: false`. The web application therefore skips the login screen and proceeds to make requests that are rejected with HTTP 401. ### Reproduction 1. Set `studio.auth.login-required=false`. 2. Persist general settings with `requireLogin=true`. 3. Call `GET /api/auth/status` without a token. 4. Observe `loginRequired: false` even though protected endpoints require a token. ### Expected behavior The public authentication status must report the effective policy: login is required when either the static property or the runtime setting enables it. ### Scope This issue only aligns the status endpoint with the effective runtime policy. It does not change authentication enforcement or authorization rules. -- 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]
