PiliLily commented on issue #427:
URL:
https://github.com/apache/rocketmq-dashboard/issues/427#issuecomment-5063748863
I would like to take a separate atomic Console authentication/authorization
slice. Scope: a real strict-bcrypt Console user registry; opaque, revocable
Bearer sessions; an exact USER route table with every other API route
defaulting to ADMIN; no RocketMQ credentials; and one atomic PR that activates
web security end to end. The file count will be larger than the usual guideline
because security responsibilities and their tests are intentionally separated.
Coordination: rebase onto #492 and #512 once they merge; for #515, include `GET
/api/clusters/{id}/capabilities` in the USER policy only if that handler is
present on the rebased base—otherwise the second PR rebased after #515 will add
the USER row in maintainer-approved ordering.
--
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]
